| 0322 stable build does not run on windows [message #22579] |
Fri, 22 March 2002 23:29  |
Eclipse User |
|
|
|
I just downloaded the latest stable build (22 March). I unzipped it, and
double clicked eclipse.exe. I get this message:
JVM Terminated. Exit Code = 2
C:\WINNT\System32\javaw.exe
classpath: C:\dev\eclipse\startup.jar org.eclipse.core.launcher.Main
-application org.eclipse.ui.workbench
-ws win32D
-endsplash C:\Dev\eclipse\eclipse.exe -endsplash 197196.
The system is a windoze 2k Ibm thinkpad.
thanks for any help.
Leon Webster
|
|
|
|
|
|
| Re: Nightly Builds [message #23213 is a reply to message #23177] |
Mon, 01 April 2002 12:43  |
| Eclipse User |
|
|
|
Originally posted by: jadb.redhat.com
Hi Jeff,
It was very refreshing to finally see a makefile somewhere in eclipse
land. I guess I missed the "getting started with CDT development" web
page that outlined the 6 step process. But at least I was able to invoke
a makefile. I discovered I couldn't run "make dev", but I could do "make
all". When I ran "make dev" I got:
"Cannot find jars from com.ibm.debug.daemon"
and in fact... I couldn't find that component either...
so once I realized that it's just not in the modules list for "cdt", I
pulled that from CVS, and it looks like it's building everything.
Now if building the 'core eclipse' was just as easy...
--
Joe
Jeff Turnham wrote:
> Hi,
>
> Just to clarify...we do provide CDT drivers that are for the Eclipse 2.0
> framework. They are found on the download page that you mention. We
> typically provide a stable tested driver once a month (the next one will
> appear before April 8).
>
> For the time being we are not providing nightly builds mainly because we do
> not yet have nightly sanity tests going...and we would not want any users to
> go through the hassle of downloading a nightly build just to have it not
> work. At a minimum we would like to provide evidence that a nightly driver
> has undergone some simple testing to make sure it is not fundamentally
> broken. Once we get that process automated internally, we would consider
> making nightly builds available.
>
> By the way, if you really want the latest and greatest CDT and can't wait
> for the stable drivers, our CVS is public and our build process is quite
> simple. Getting and building the CDT would only require the following
> (assuming you're on linux):
>
> 1. Make sure you have a jdk that is at least version 1.3
> 2. export CVSROOT=:pserver:anonymous@dev.eclipse.org:/home/tools
> 3. Goto the <..>/eclipse/plugins directory
> 4. cvs checkout cdt
> 5. cd org.eclipse.cdt.dstore.core
> 6. make dev
>
> "Joe deBlaquiere" <jadb@redhat.com> wrote in message
> news:3CA72D72.4000608@redhat.com...
>
>>Are there nightly builds of the CDT available? If so, where?
>>
>>I went to the download page looking for them at:
>>
>>
>>
> http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt- home/downloads/m
> ain.html?cvsroot=Tools_Project
>
>>but didn't find anything like that. In particular, I was hoping to start
>>working with the CDT on the Eclipse 2.0 framework.
>>
>>Thanks in advance for the help...
>>
>>--
>>Joe
>>
>>
>
>
|
|
|
| Re: Nightly Builds [message #23264 is a reply to message #23213] |
Mon, 01 April 2002 14:16 |
| Eclipse User |
|
|
|
Hi Joe,
Sorry about that...I had put a request into our cvs admin a few days ago to
get the com.ibm.debug.daemon added to the cdt-debug module and forgot to
check to make sure it was in there before giving you those instructions, but
I see it just made it in today (Probably five minutes after you checked it
out explicitly ;-).
Also, just a heads up, we are currently making changes to adapt to changes
made for the latest Stable Eclipse Driver (20020321), so there may be some
functionality (specifically in the editor and debugger) that might be
temporarily broken. Are you subscribed to the cdt-dev mailing list? If so,
I'll post a note when the code in cvs should be fully ready for the 20020321
(and probably later) Eclipse drivers.
Thanks...
Jeff Turnham
"Joe deBlaquiere" <jadb@redhat.com> wrote in message
news:3CA89C31.8060505@redhat.com...
> Hi Jeff,
>
> It was very refreshing to finally see a makefile somewhere in eclipse
> land. I guess I missed the "getting started with CDT development" web
> page that outlined the 6 step process. But at least I was able to invoke
> a makefile. I discovered I couldn't run "make dev", but I could do "make
> all". When I ran "make dev" I got:
>
> "Cannot find jars from com.ibm.debug.daemon"
>
> and in fact... I couldn't find that component either...
>
> so once I realized that it's just not in the modules list for "cdt", I
> pulled that from CVS, and it looks like it's building everything.
>
> Now if building the 'core eclipse' was just as easy...
>
> --
> Joe
>
> Jeff Turnham wrote:
>
> > Hi,
> >
> > Just to clarify...we do provide CDT drivers that are for the Eclipse 2.0
> > framework. They are found on the download page that you mention. We
> > typically provide a stable tested driver once a month (the next one will
> > appear before April 8).
> >
> > For the time being we are not providing nightly builds mainly because we
do
> > not yet have nightly sanity tests going...and we would not want any
users to
> > go through the hassle of downloading a nightly build just to have it not
> > work. At a minimum we would like to provide evidence that a nightly
driver
> > has undergone some simple testing to make sure it is not fundamentally
> > broken. Once we get that process automated internally, we would
consider
> > making nightly builds available.
> >
> > By the way, if you really want the latest and greatest CDT and can't
wait
> > for the stable drivers, our CVS is public and our build process is quite
> > simple. Getting and building the CDT would only require the following
> > (assuming you're on linux):
> >
> > 1. Make sure you have a jdk that is at least version 1.3
> > 2. export CVSROOT=:pserver:anonymous@dev.eclipse.org:/home/tools
> > 3. Goto the <..>/eclipse/plugins directory
> > 4. cvs checkout cdt
> > 5. cd org.eclipse.cdt.dstore.core
> > 6. make dev
> >
> > "Joe deBlaquiere" <jadb@redhat.com> wrote in message
> > news:3CA72D72.4000608@redhat.com...
> >
> >>Are there nightly builds of the CDT available? If so, where?
> >>
> >>I went to the download page looking for them at:
> >>
> >>
> >>
> >
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt- home/downloads/m
> > ain.html?cvsroot=Tools_Project
> >
> >>but didn't find anything like that. In particular, I was hoping to start
> >>working with the CDT on the Eclipse 2.0 framework.
> >>
> >>Thanks in advance for the help...
> >>
> >>--
> >>Joe
> >>
> >>
> >
> >
>
|
|
|
| Re: Nightly Builds [message #23278 is a reply to message #23213] |
Mon, 01 April 2002 14:54 |
| Eclipse User |
|
|
|
Hi Again,
The fact that your "make dev" failed will mean that your build of the cdt
will not work. "make all" will simply attempt to build the
org.eclipse.cdt.dstore.core directory and will also not really work since it
assumes that a "make dev" has been done.
Let me step back and explain a little bit about that makefile.
Currently only a subset of the CDT plugins need to be built. The LPEX
Editor plugin and the Debug plugins are not built since they already contain
pre-built jars. This is because we get them from other teams with other
build processes. It is possible that we will change things so that
everything gets built out of our cvs (for consistency).
There is only 1 makefile for all of the CDT in CVS and that is
org.eclipse.cdt.dstore.core/makefile. This makefile is used to generate
makefiles for all the plugins in the CDT. The command to do this is "make
dev". This actually goes into the "build" sub-directory and compiles\runs
GenerateMakefiles.java which is a utility that creates simple makefiles in
every sub-directory of every plugin that needs to be built in the CDT. The
unfortunate thing is that this requires you have your PATH pointing to a jdk
somewhere. I am going to open a feature against myself to look at replacing
this with a perl script. I suspect this is what your problem with running
"make dev" was. If not, then can you provide a copy of the output of the
failed command.
Once all sub-directories have makefiles, "make dev" then starts a build of
all "buildable" CDT plugins. Once "make dev" has finished, you then have a
complete build enviroment. For example you then can browse to any directory
that has CDT source and type "make" to build just from that directory. This
process has worked well for us internally but has not been exercised in
different environments. Please feel free to send us your
comments\suggestions. Actually the cdt-dev mailing list would be a more
appropriate place than this newsgroup.
Hope that helps...
Jeff Turnham
"Joe deBlaquiere" <jadb@redhat.com> wrote in message
news:3CA89C31.8060505@redhat.com...
> Hi Jeff,
>
> It was very refreshing to finally see a makefile somewhere in eclipse
> land. I guess I missed the "getting started with CDT development" web
> page that outlined the 6 step process. But at least I was able to invoke
> a makefile. I discovered I couldn't run "make dev", but I could do "make
> all". When I ran "make dev" I got:
>
> "Cannot find jars from com.ibm.debug.daemon"
>
> and in fact... I couldn't find that component either...
>
> so once I realized that it's just not in the modules list for "cdt", I
> pulled that from CVS, and it looks like it's building everything.
>
> Now if building the 'core eclipse' was just as easy...
>
> --
> Joe
>
> Jeff Turnham wrote:
>
> > Hi,
> >
> > Just to clarify...we do provide CDT drivers that are for the Eclipse 2.0
> > framework. They are found on the download page that you mention. We
> > typically provide a stable tested driver once a month (the next one will
> > appear before April 8).
> >
> > For the time being we are not providing nightly builds mainly because we
do
> > not yet have nightly sanity tests going...and we would not want any
users to
> > go through the hassle of downloading a nightly build just to have it not
> > work. At a minimum we would like to provide evidence that a nightly
driver
> > has undergone some simple testing to make sure it is not fundamentally
> > broken. Once we get that process automated internally, we would
consider
> > making nightly builds available.
> >
> > By the way, if you really want the latest and greatest CDT and can't
wait
> > for the stable drivers, our CVS is public and our build process is quite
> > simple. Getting and building the CDT would only require the following
> > (assuming you're on linux):
> >
> > 1. Make sure you have a jdk that is at least version 1.3
> > 2. export CVSROOT=:pserver:anonymous@dev.eclipse.org:/home/tools
> > 3. Goto the <..>/eclipse/plugins directory
> > 4. cvs checkout cdt
> > 5. cd org.eclipse.cdt.dstore.core
> > 6. make dev
> >
> > "Joe deBlaquiere" <jadb@redhat.com> wrote in message
> > news:3CA72D72.4000608@redhat.com...
> >
> >>Are there nightly builds of the CDT available? If so, where?
> >>
> >>I went to the download page looking for them at:
> >>
> >>
> >>
> >
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt- home/downloads/m
> > ain.html?cvsroot=Tools_Project
> >
> >>but didn't find anything like that. In particular, I was hoping to start
> >>working with the CDT on the Eclipse 2.0 framework.
> >>
> >>Thanks in advance for the help...
> >>
> >>--
> >>Joe
> >>
> >>
> >
> >
>
|
|
|
Powered by
FUDForum. Page generated in 0.03621 seconds
Home