Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Equinox p2 - Building"
Line 25: | Line 25: | ||
Then from the command-line, run the appropriate build file: either <code>build_win.bat</code> or <code>build_lnx</code>. | Then from the command-line, run the appropriate build file: either <code>build_win.bat</code> or <code>build_lnx</code>. | ||
− | + | ''Note:'' you must have the CVS executable available from the command-line in order for the checkout to work. | |
===Output=== | ===Output=== | ||
− | * The Agent zip will be in | + | * The Agent zip will be in ''${prov.output.base}/equinox-prov-agent-<timestamp>-win32.zip'' |
− | * The Metadata and Artifact repositories will be in ${prov.output.base}/servers | + | * The Metadata and Artifact repositories will be in ''${prov.output.base}/servers'' |
===What Happens=== | ===What Happens=== |
Revision as of 16:03, 23 August 2007
This page contains information on how to build the Equinox Provisioning code.
Contents
Workspace Setup
A project has been created in CVS which contains a builder and the build scripts for the new provisioning work. Check out the project from CVS with the following information:
server: dev.eclipse.org repository: /cvsroot/eclipse project: /equinox-incubator/provisioning/org.eclipse.equinox.prov.releng.builder
There is a builder
sub-directory which contains an Eclipse install with the minimal bundles required to run the build. It is a Window build and should be replaced with a Linux drop if that is appropriate for the machine that you are running on.
Open the run.xml
file for editing. There are a few properties in here that you will have to modify.
<property name="prov.root" value="c:" /> <property name="prov.output.base" value="${prov.root}/equinox.prov.build" /> <property name="sdk.archive" value="${prov.root}/downloads/eclipse-SDK-3.4M1-win32.zip" /> <property name="rcp.delta.archive" value="${prov.root}/downloads/eclipse-RCP-3.4M1-delta-pack.zip" /> <property name="rcp.archive" value="${prov.root}/downloads/eclipse-RCP-3.4M1-win32.zip" /> <property name="prov.java" value="d:/java/jdk1.5.0_11/jre/bin/java" />
Then from the command-line, run the appropriate build file: either build_win.bat
or build_lnx
.
Note: you must have the CVS executable available from the command-line in order for the checkout to work.
Output
- The Agent zip will be in ${prov.output.base}/equinox-prov-agent-<timestamp>-win32.zip
- The Metadata and Artifact repositories will be in ${prov.output.base}/servers
What Happens
- build features for the director, metadata generator, and self-hosting bundles
- build the agent from a product
- generate the metadata for the agent
- run the director and install the agent from the generated metadata and artifacts
- zip up the agent install
- generate the metadata for the self-hosting bundles and Eclipse SDK
TODO
- integrate with the regular Platform builds
- write code to determine the output file of the build
- should enhance so instead of building several different things, we should build one big feature and then use the packager to put together the things that we need