| build and release process for eclipse [message #328512] |
Mon, 26 May 2008 19:58  |
Eclipse User |
|
|
|
Hello,
What is the standard way for me to get the source and build it from
scratch?
I've started using cvs to checkout the modules. That was very confusing
because there were so many modules to play with. After getting a few
files here and there, I couldn't find an entry point to do a "make".
Eventually I got hold of the srcInclude with file name extention
-I20080415-1646.zip. I've built that with compile error, submitted a bug
and waited a few weeks. After that I see that the srcInclude has a link
with status such as "build failed status". I waited for a good build but
even that got an error as well. Eventually that link went away
entirely. I could only get a build called a nice even release number
called srcIncluded-3.3.zip. However that one came with error below.
Also I came across the news group called eclipse.release or something
along that line, but I couldn't find that newsgroup, so now I have to
resort to this one.
[javac] return (IPluginReference[]) result.toArray(new
IPluginReference[
result
[javac] .size()]);
[javac]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^
[javac] Type safety: The method toArray(Object[]) belongs to the
raw type Ar
rayList. References to generic type ArrayList<E> should be parameterized
[javac] ----------
[javac] 45 problems (45 warnings)
[echo] Assembling...
[exec]
[exec] zip error: Nothing to do! (try: zip -r -q -qq
C:\dev\cvs2\ball3/resu
lt/org.eclipse.sdk-I20070625-1500-win32.win32.x86.zip . -i .)
[exec] Result: 12
Eventually I want to see a documentation on how the build command
traverses the directory and compile the code in certain order and what
the module means, but that's a much later step.
|
|
|
| Re: build and release process for eclipse [message #328553 is a reply to message #328512] |
Tue, 27 May 2008 11:47  |
| Eclipse User |
|
|
|
Derek,
The standard way to build it yourself is to get the source build. Every
eclipse download page (for example RC2:
http://download.eclipse.org/eclipse/downloads/drops/S-3.4RC2 -200805230100/index.php)
has a link to the "Source Builds page"
http://download.eclipse.org/eclipse/downloads/drops/S-3.4RC2 -200805230100/sourceBuilds.php
Which is where you would have found your srcInclude. There are
instructions links beside the download links that might help you.
I would suggest your compile errors have to do with your bootclasspath.
The normal Eclipse builds actually specify multiple bootclasspaths
corresponding to Execution environments used by individual bundles.
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. pde.doc.user/guide/tasks/pde_compilation_env.htm
However, I don't know how this is handled in the source build.
-Andrew
Derek wrote:
> Hello,
> What is the standard way for me to get the source and build it from
> scratch?
>
>
> I've started using cvs to checkout the modules. That was very confusing
> because there were so many modules to play with. After getting a few
> files here and there, I couldn't find an entry point to do a "make".
>
>
> Eventually I got hold of the srcInclude with file name extention
> -I20080415-1646.zip. I've built that with compile error, submitted a bug
> and waited a few weeks. After that I see that the srcInclude has a link
> with status such as "build failed status". I waited for a good build but
> even that got an error as well. Eventually that link went away
> entirely. I could only get a build called a nice even release number
> called srcIncluded-3.3.zip. However that one came with error below.
>
> Also I came across the news group called eclipse.release or something
> along that line, but I couldn't find that newsgroup, so now I have to
> resort to this one.
>
>
>
> [javac] return (IPluginReference[]) result.toArray(new
> IPluginReference[
> result
> [javac] .size()]);
> [javac] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^^^^^^^^^^^^^^^^^^^
> [javac] Type safety: The method toArray(Object[]) belongs to the raw
> type Ar
> rayList. References to generic type ArrayList<E> should be parameterized
> [javac] ----------
> [javac] 45 problems (45 warnings)
> [echo] Assembling...
> [exec]
> [exec] zip error: Nothing to do! (try: zip -r -q -qq
> C:\dev\cvs2\ball3/resu
> lt/org.eclipse.sdk-I20070625-1500-win32.win32.x86.zip . -i .)
> [exec] Result: 12
>
>
> Eventually I want to see a documentation on how the build command
> traverses the directory and compile the code in certain order and what
> the module means, but that's a much later step.
|
|
|
Powered by
FUDForum. Page generated in 0.06300 seconds
Home