-
Notifications
You must be signed in to change notification settings - Fork 89
Build System
<wiki:toc />
This project has 3 build systems:
- Development CDT
- Development NAR
- Production NAR
each build system will produce artifacts with specific names and at specific locations which are arch and os dependent; barchart-udt native libarary loader will use the following search priority when looking for these artifacts:
- Production NAR
- Development CDT
- Development NAR
you may want to delete specific artifact and/or location to force your java tests run only against the native artifacts you are interested in at the moment;
use 64 bit os;
use multi-libs;
sudo apt-get install gcc build-essential libc6-dev ia32-libs g++-multilib libc6-dev-i386
use 64 bit os;
use xcode;
use 64 bit os;
use tdm-gcc with install in c:\mingw32 & c:\mingw64;
use eclipse [launch script] (http://code.google.com/p/barchart-udt/source/browse/trunk/barchart-udt4-parent/barchart-udt4/build/hudson/slave-job-windows-gpp.cmd) to set PATH for mingw32 or mingw64;
install both 32 and 64 bit java in separate folders;
do not include either java on the path;
macosx java comes as "bundle"; regardles of what (32/64 java) is active on your system by default you must explicitly provide -d32 / -d64 for all java invocations for this project;
use eclipse pulse
ask for current barchart-udt pulse-eclipse profile to be shared for you;
setup both 32 and 64 bit jre in your eclipse under the names "java32" and "java64"; macosx needs -d32 or -d64 options;
eclipse itself must run on top of JDK, not JRE;
used for interactive development of both java and c++ code inside eclipse; allows to handle only single target os at a time; allows to test both 32/64 bits builds on the same os;
you must have eclipse cdt installed in your eclipse before you will be able to see cdt project configuration settings;
you must also activate [eclipse cdt perspective] (http://www.ibm.com/developerworks/opensource/library/os-eclipse-stlcdt/fig08.jpg) ;
you must select your matching [build configuration] (http://wiki.eclipse.org/images/f/ff/New_cdtwsconfig_wsContextMenu.png) Project->Build Configurations->Set Active->cdt-{arch}-{os}-gpp
there are 6 cdt configs in this project (for each arch and os):
- cdt_i386-Linux-gpp
- cdt_amd64-Linux-gpp
- cdt_i386-MacOSX-gpp
- cdt_x86_64-MacOSX-gpp
- cdt_x86-Windows-gpp
- cdt_amd64-Windows-gpp
when cdt makes a build, you will see that a resource folder appears in you project with the same name as configuraton name; if you want cdt to re-build given configuration w/o "project clean" - just delete the resource folder; this folder is not part of source repository;
you must select active build configuration that matches your platform arch and current java bitness (32 vs 64);
you must have 2 named java jre defined in your eclipse: "java32" and "java64" (on macosx you must provide -d32/-d64 options to your java)
you must map one of these java jre to the "java se 1.6" in your eclipse;
every time you update/save your java / c++ code in eclipse the following will happen:
- java will get compiled and placed in target/classes
- c++ will get compiled and placed in cdt-{arch}-{os}-gpp folder as well as into target/test-classes
- console will show c++ build errors, if any;
- double-click on the highlighted c++ console error will bring you back to the c++ source at the location of the error;
to disspell the black magic of cdt build, take a look here:
Project->Properties->Builders;
you will see, that when eclipse detects change, the following steps are performed:
- Java Builder (provided by [http://www.eclipse.org/jdt/ JDT], runs incremental javac)
- [Eclipse_JNI_Build] (http://code.google.com/p/barchart-udt/source/browse/trunk/barchart-udt4-parent/barchart-udt4/build/script/eclipse-builder.ant) (provided by this project, runs incremental javah)
- CDT Builder (provided by CDT, runs incremental gcc)
- [Eclipse_LIB_Copy] (http://code.google.com/p/barchart-udt/source/browse/trunk/barchart-udt4-parent/barchart-udt4/build/script/eclipse-builder.ant) (provided by this project, runs artifact copy)
- Scanner Configuration Builder (provided by CDT, runs cdt parsers)
- Maven Project Builder (provided by M2E, copies extra resources as defined in pom.xml)
location of "development cdt" native libs:
${project}/target/test-classes/
used for verification that maven-nar-plugin settings match to cdt settings; and that both cdt and nar produce identical libraries/artifacts;
[current nar settings] (http://code.google.com/p/barchart-udt/source/browse/trunk/barchart-udt4-parent/barchart-udt4/aol.properties)
there are numerous "maven launch configurations" provided for various maven-related tasks; study them and create your own;
for example:
- "barchart-udt4_nar_macosx-32.m2e" will produce "development nar" libraries;
- "barchart-udt4_test-macosx-32.m2e" will run all unit tests;
you must run appropriate version of m2e plugin in your eclipse;
you must have appropriate version on maven installed in /opt/apache-maven-3.0.4
alternatively, you do not have to have eclipse to run these builds; you can run these maven builds from command line;
location of "development nar" native libs (example):
${project}/target/test-classes/barchart-udt4-1.0.3-SNAPSHOT-i386-Linux-gpp-jni/lib/i386-Linux-gpp/jni
used for multi-platform jenkins auto build with maven-nar-plugin;
the process involves brining up all target platforms (hudson slaves in vm), building libraries, running unit tests, running integration tests, and uploading jars and nars to the snapshot repo;