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"
| Line 6: | Line 6: | ||
==Process== | ==Process== | ||
====Identify affected platforms==== | ====Identify affected platforms==== | ||
| − | 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] | + | 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 | : library - contains common code | ||
:: cocoa - contains Mac specific code | :: cocoa - contains Mac specific code | ||
| Line 16: | Line 16: | ||
====Identify whether build id needs to increment==== | ====Identify whether build id needs to increment==== | ||
You need to compare last build id | You need to compare last build id | ||
| − | + | * used in the last successful build of launcher across all platforms and | |
| − | : used for that specific platform | + | :: Can be identified by the variable LIB_VERSION in [https://git.eclipse.org/c/equinox/rt.equinox.framework.git/tree/features/org.eclipse.equinox.executable.feature/library/make_version.mak make_version.mak] |
| + | * used for that specific platform | ||
| + | :: Verify platform specific eclipse_<version>.<so/dll> at [https://git.eclipse.org/c/equinox/rt.equinox.binaries.git/tree/ binaries repo] eclipse_<version>.<so/dll> would be present in org.eclipse.equinox.launcher.<ws>.<os>.<arch> | ||
If both are same you'll need to increment, otherwise build id should not be incremented | If both are same you'll need to increment, otherwise build id should not be incremented | ||
| − | + | ====Execution of build jobs==== | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ===Execution of build jobs=== | + | |
Run the [https://hudson.eclipse.org/releng/view/Launcher/job/Step-1-Increment-build-id/ Step-1-Increment-build-id] in the next page it asks for 4 options. | Run the [https://hudson.eclipse.org/releng/view/Launcher/job/Step-1-Increment-build-id/ 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) | * increment build id (check this if you have determined the build_id needs to be incremented) | ||
| Line 36: | Line 30: | ||
* buildWin32 (check this for windows 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/ | + | 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/ collect libraries job] 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 [https://hudson.eclipse.org/releng/view/Launcher/job/Step-2-Commit-libraries-and-push/ Step-2-Commit-libraries-and-push]. This will push newly built libraries to git repos. | Wait for the collect-launcher-libs jobs to complete and also check for any failures. If there are no failures run [https://hudson.eclipse.org/releng/view/Launcher/job/Step-2-Commit-libraries-and-push/ Step-2-Commit-libraries-and-push]. This will push newly built libraries to git repos. | ||
Revision as of 07:59, 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
- Can be identified by the variable LIB_VERSION in make_version.mak
- used for that specific platform
- Verify platform specific eclipse_<version>.<so/dll> at binaries repo eclipse_<version>.<so/dll> would be present in org.eclipse.equinox.launcher.<ws>.<os>.<arch>
If both are same you'll need to increment, otherwise build id should not 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 collect libraries job 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.