Another thing you can do, if all you're after is getting your changes installed in your local eclipse instance, is export into the current host environment:
On 13 Jan 2010, at 20:04, Vivian Kong <vivkong@xxxxxxxxxx> wrote:
The easiest way to do that is to use the Export wizard.
For example, to build the org.eclipse.cdt feature (I'm using Eclipse 3.6M3):
1. Select org.eclipse.cdt.feature in your workspace and select Export:
2. Select Deployable features, click Next
3. Select the feature(s) you want to deploy and specify the destination:
4. Click Finish. It took approx 3-5 mins for this to finish.
You can then find the feature and plugin jars in the location you specified.
5. Copy the following exported directories/files to the dropins/eclipse folder of an Eclipse build. This will install the CDT feature.
IBM Eclipse CDT
IBM Canada Toronto Lab
<graycol.gif>David Sariel ---01/13/2010 12:16:45 PM---Hi, Have anybody ever tried to build CDT distribution from local sources
David Sariel <datosar@xxxxxxxxx>
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
01/13/2010 12:16 PM
[cdt-dev] Re: building the CDT
Have anybody ever tried to build CDT distribution from local sources
spearing fetching sources from dev.eclipse.org:/cvsroot/tools CVS
I tried to change map.cdt file to fetch sources I have changed from my
CVS repository and it doesn't work.
I also tried to figure out (using printouts) how org.eclipse.cdt.releng
work and lost the track. I don't understand how packages listed in
cdt.map are fetched from the CVS. The build process fetches them in
completely different order. Also I don't understand where from
“fetch_<package_name>.xml” files creation is guided from.
I thought I will be easily able to change scripts to either fetch files
from my CVS repository or by simply taking my local source files. And
both seem to complicated.
I will very much appreciate if someone can explain how to produce
distribution files from local sources (without CVS).
I found post from 2002
with the list of steps to build CDT without fetching files from CVS.
According to it, I tried to import :
into my workspace (together with the packages they depend on) and then
to export everything as “deployable plug-ins and packages” (eclipse
plug-in development option). But it doesn't work.
Sorry for the long post and thanks in advance,
David Sariel wrote:
> Sorry for beginners question, but I want to be sure I'm in the right direction.
> During the development process I was running the CDT from eclipse as
> eclipse application.
> I understand that if I want to run CDT without running it from another
> instance of eclipse,
> I have to build it with org.eclipse.cdt.releng scripts. But is that
> the only way?
> For example, can't I just choose export and then select to create
> deployable plugins or
> eclipse product?
> In case the answer to the previous question is negative and the only
> resort is to use the org.eclipse.cdt.releng build scripts , how can I
> avoid fetching files from CVS server that is performed by
> org.eclipse.cdt.releng? I understand that I can refer in cdt.map to my
> CVS repository that contains my version of CDT sources, but is there
> exists an easier way to build CDT from the sources that are located on
> my HD without setting up CVS and rewriting cdt.map?
cdt-dev mailing list
cdt-dev mailing list