Changes between Version 11 and Version 12 of compile_all

Timestamp:

Feb 13, 2019, 5:22:22 PM (6 years ago)

Author:

Sanahuja Guillaume

Comment:

--

compile_all

@@ -90 +90 @@
 ''project_path'' depends on what you are compiling:
 
-* ''!FlairLibs/lib'': a flair library (for example ''!FlairLibs/FlairCore'')
-* ''tools/tool'': a flair tool (for example ''tools/FlairGCS'')
-* ''demos/demo'': a flair demo (for example ''demos/CircleFollower''). Not that you can also have subfolders like ''demos/CircleFollower/simulator'' or ''demos/CircleFollower/uav'' if you want to compile just simulator or uav project
+* ''!FlairLibs/<lib>'': a flair library (for example ''!FlairLibs/FlairCore'')
+* ''tools/<tool>'': a flair tool (for example ''tools/FlairGCS'')
+* ''demos/<demo>'': a flair demo (for example ''demos/CircleFollower''). Not that you can also have subfolders like ''demos/CircleFollower/simulator'' or ''demos/CircleFollower/uav'' if you want to compile just simulator or uav project
 
 For Heudiasyc users ''project_path'' can also be the following:
 
-* ''flair-hds/FlairHdsLibs/lib'': a flair hds library (for example ''flair-hds/FlairHdsLibs/FlairArdrone2'')
-* ''flair-hds/demos/demo'': a flair hds demo (for example ''flair-hds/demos/ApriltagFollower''). Not that you can also have subfolders like ''flair-hds/demos/ApriltagFollower/simulator'' or ''flair-hds/demos/ApriltagFollower/uav'' if you want to compile just simulator or uav project
+* ''flair-hds/FlairHdsLibs/<lib>'': a flair hds library (for example ''flair-hds/FlairHdsLibs/FlairArdrone2'')
+* ''flair-hds/demos/<demo>'': a flair hds demo (for example ''flair-hds/demos/ApriltagFollower''). Not that you can also have subfolders like ''flair-hds/demos/ApriltagFollower/simulator'' or ''flair-hds/demos/ApriltagFollower/uav'' if you want to compile just simulator or uav project
 
 == Compile your own project == 
@@ -103 +103 @@
 __NOTE__: this is also works for projects provided in ''flair-src'' and ''flair-hds'' repositories. 
 
+You can generate your own project where you want, and compile it. Yet, you need to have [wiki:compile_all#CompileFlairlibrariestoolsanddemosalltogether compiled and installed] Flair libs before to have all needed development files. But it is not necessary to recompile libs each time you want to compile your project!
+
+The following assumes that your project is in ''$FLAIR_ROOT/<path_to_my_project>'' and you want to built it in ''$FLAIR_ROOT/flair-build/<mywork>/<myproject>''
+{{{
+$ mkdir -p $FLAIR_ROOT/flair-build/<mywork>/<myproject>
+$ cd $FLAIR_ROOT/flair-build/<mywork>/<myproject>
+$ $FLAIR_ROOT/flair-dev/scripts/cmake_codelite_outofsource.sh $FLAIR_ROOT/<path_to_my_project>
+$ cd build
+$ make install
+}}}
+
+It will compile for x86_64 architecture. To compile for a different architecture, go to the corresponding directory, for example:
+{{{
+$ cd build_armv5te
+or
+$ cd build_armv7a_neon
+or
+$ cd build_cortexa7thf_neon_vfpv4
+}}}
 
 == Compilation with debug (optional) ==