[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-dev] Re: Nightly Builds
|
OK, moving to cdt-dev...
Jeff Turnham wrote:
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.
after "cvs co com.ibm.debug.daemon" and a "make clean-dev", "make dev"
now works. The slightly revised process is:
1. Make sure you have a jdk that is at least version 1.3
2. export CVSROOT=:pserver:anonymous@xxxxxxxxxxxxxxx:/home/tools
3. Goto the <..>/eclipse/plugins directory
4. cvs checkout cdt com.ibm.debug.daemon
5. cd org.eclipse.cdt.dstore.core
6. make dev
It had a problem building org.eclipse.cdt.cpp.ui... so I did:
7. cd ../org.eclipse.cdt.cpp.ui
8. make clean
8. make
at which point it failed (as you explained, it's currently unstable, so
this was expected). At least I can now start to look at java bugs that
are probably beyond my near-term comprehension... I attached a log in
case anybody is curious...
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).
so I assume that there is a similar 6 step process for LPEX and Debug?
Is anybody looking at unifying the build process?
I realize that doing a complete build from source is on the schedule,
but if we get there sooner rather than later it will be easier for
people to get started with Eclipse.
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.
alternatively, you could just try and run javac -help and print a "can't
find javac, is JDK in PATH?" error...
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.
So is there a way to traverse all of the CDT plugins and "make" in all
of them? I thought that's what make dev did, but it doesn't sound like
it from your paragraph.
Hope that helps...
Jeff Turnham
"Joe deBlaquiere" <jadb@xxxxxxxxxx> wrote in message
news:3CA89C31.8060505@xxxxxxxxxx...
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@xxxxxxxxxxxxxxx:/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@xxxxxxxxxx> wrote in message
news:3CA72D72.4000608@xxxxxxxxxx...
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
make[1]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org'
make[2]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse'
make[3]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt'
make[4]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp'
make[5]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui'
make[6]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui/internal'
make[7]: Entering directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui/internal/actions'
Compiling AddClassBreakpoint.java
Compiling AdvancedConfigureAction.java
/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.dstore.ui/org/eclipse/cdt/dstore/ui/resource/FileResourceElement.java:35: org.eclipse.cdt.dstore.ui.resource.FileResourceElement should be declared abstract; it does not define appendContents(java.io.InputStream,int,org.eclipse.core.runtime.IProgressMonitor) in org.eclipse.cdt.dstore.ui.resource.FileResourceElement
public class FileResourceElement extends ResourceElement implements IFile
^
/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.dstore.ui/org/eclipse/cdt/dstore/ui/resource/FolderResourceElement.java:31: org.eclipse.cdt.dstore.ui.resource.FolderResourceElement should be declared abstract; it does not define create(int,boolean,org.eclipse.core.runtime.IProgressMonitor) in org.eclipse.cdt.dstore.ui.resource.FolderResourceElement
public class FolderResourceElement extends ResourceElement implements IFolder
^
2 errors
make[7]: *** [AdvancedConfigureAction.class] Error 1
make[7]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui/internal/actions'
make[6]: *** [actions_dir] Error 2
make[6]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui/internal'
make[5]: *** [internal_dir] Error 2
make[5]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp/ui'
make[4]: *** [ui_dir] Error 2
make[4]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt/cpp'
make[3]: *** [cpp_dir] Error 2
make[3]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse/cdt'
make[2]: *** [cdt_dir] Error 2
make[2]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org/eclipse'
make[1]: *** [eclipse_dir] Error 2
make[1]: Leaving directory `/home/jadb/projects/gtk_eclipse/eclipse-20020321-gtk/eclipse/plugins/org.eclipse.cdt.cpp.ui/org'
make: *** [org_dir] Error 2
