See baseline-compare-and-replaceīaseline-compare-and-replace profile controls whether baseline replace and compare is performed. The CI build uses this to speedup turnaround on changes only affecting the terminal. A special terminal only p2 site is created in terminal/repo/target/repository. The allows running maven like this mvn -f terminal/pom.xml verify -P only-terminal to build and test only the terminal and its dependencies. The terminal directory has a special profile that enables only the terminal and its dependencies when used. The CI build uses this to parallelize tests. Using any of the above profiles can skip large sets of tests. Using the build-standalone-debugger-rcp profile will include the standalone debugger, located in debug/.application.product skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-lsp, skip-tests-except-cdt-other build the standalone rcp debugger against the latest simrel mvn verify -DuseSimrelRepo -f debug/.application.product.test CDT against a pre-built CDT by using the cdtRepo profile.
Individual p2 repos can be turned on and off to allow building CDT, or parts of CDT against different target platforms easily. There are a number of profiles (-P to mvn) to control the behaviour of the build. Refer to the Dockerfiles for the current versions of those dependencies. The requirements for running all tests successfully and for rebuilding non-Java parts of CDT are much more extensive than standard Maven & Java and include items such as GCC, GDB, yarn, Node, etc. The Dockerfiles used for CDT's images are published in cdt-infra. To build CDT plug-ins you need a standard Maven & Java developement environment.
The current set of options to Maven used for building on the CI can be seen in the Jenkinsfiles on cdt-infra Therefore to package CDT do: mvn packageĪnd the resulting p2 repository will be in releng//target/repository
Command-line Build instructions with MavenĮclipse CDT uses the standard Maven and Tycho workflow for building CDT using Maven 3.6.0 and Java 8. Most developers, developing CDT in the Eclipse IDE, should use Getting_started_with_CDT_development. Please see CONTRIBUTING.md for contributing information Developing CDT
0 kommentar(er)
