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 "Building Equinox Launcher"
(→Process) |
|||
| Line 5: | Line 5: | ||
==Process== | ==Process== | ||
| − | + | ====Identify affected platforms==== | |
| − | - Identify the last built build-id for that specific platform | + | The library source structure is (can be seen here [https://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/features/org.eclipse.equinox.executable.feature/library Launcher Source] |
| − | + | : library - contains common code | |
| − | + | :: cocoa - contains Mac specific code | |
| − | + | :: gtk - contains Linux specific code | |
| + | :: win32 - contains Windows specific code | ||
| + | |||
| + | If common code is changed you need to build all platforms. Otherwise only the specific platforms needs to built | ||
| + | |||
| + | ====Identify whether build id needs to increment==== | ||
| + | You need to compare last build id | ||
| + | : used in the last successful build of launcher across all platforms and | ||
| + | : used for that specific platform | ||
| + | |||
| + | If both are same you'll need to increment, otherwise build id should not be incremented | ||
| + | |||
| + | |||
| + | * Identify the last built build-id for that specific platform | ||
| + | ** Can be identified by https://git.eclipse.org/c/equinox/rt.equinox.binaries.git/tree/org.eclipse.equinox.launcher.<ws>.<os>.<arch>/eclipse_<build id>.<so/dll> | ||
| + | * Identify last build id used for building any launcher platform | ||
| + | ** Available here https://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/features/org.eclipse.equinox.executable.feature/library/make_version.mak | ||
if both are same then the build_id needs to be incremented. | if both are same then the build_id needs to be incremented. | ||
Revision as of 07:42, 23 January 2018
Equinox Launchers can be built from Releng CI Instance. This needs to be used on demand only.
https://hudson.eclipse.org/releng/view/Launcher/job/Step-1-Increment-build-id/
Contents
Process
Identify affected platforms
The library source structure is (can be seen here Launcher Source
- library - contains common code
- cocoa - contains Mac specific code
- gtk - contains Linux specific code
- win32 - contains Windows specific code
If common code is changed you need to build all platforms. Otherwise only the specific platforms needs to built
Identify whether build id needs to increment
You need to compare last build id
- used in the last successful build of launcher across all platforms and
- used for that specific platform
If both are same you'll need to increment, otherwise build id should not be incremented
- Identify the last built build-id for that specific platform
- Can be identified by https://git.eclipse.org/c/equinox/rt.equinox.binaries.git/tree/org.eclipse.equinox.launcher.<ws>.<os>.<arch>/eclipse_<build id>.<so/dll>
- Identify last build id used for building any launcher platform
if both are same then the build_id needs to be incremented.
Execution of build jobs
Run the Step-1-Increment-build-id in the next page it asks for 4 options.
* increment build id (check this if you have determined the build_id needs to be incremented) * buildGtk (check this if linux platforms needs to be built) * buildCocoa (check this for Macos platforms) * buildWin32 (check this for windows platforms)
After this click on build button. then build will start and you'll see [https://hudson.eclipse.org/releng/view/Launcher/job/collect-launcher-libs/ scheduled multiple times(4 times for gtk, 2 for win32 and 1 for Mac).
Wait for the collect-launcher-libs jobs to complete and also check for any failures. If there are no failures run Step-2-Commit-libraries-and-push. This will push newly built libraries to git repos.