Changes between Version 11 and Version 12 of compile_all


Ignore:
Timestamp:
Feb 13, 2019, 5:22:22 PM (21 months ago)
Author:
Sanahuja Guillaume
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • compile_all

    v11 v12  
    9090''project_path'' depends on what you are compiling:
    9191
    92 * ''!FlairLibs/lib'': a flair library (for example ''!FlairLibs/FlairCore'')
    93 * ''tools/tool'': a flair tool (for example ''tools/FlairGCS'')
    94 * ''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
     92* ''!FlairLibs/<lib>'': a flair library (for example ''!FlairLibs/FlairCore'')
     93* ''tools/<tool>'': a flair tool (for example ''tools/FlairGCS'')
     94* ''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
    9595
    9696For Heudiasyc users ''project_path'' can also be the following:
    9797
    98 * ''flair-hds/FlairHdsLibs/lib'': a flair hds library (for example ''flair-hds/FlairHdsLibs/FlairArdrone2'')
    99 * ''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
     98* ''flair-hds/FlairHdsLibs/<lib>'': a flair hds library (for example ''flair-hds/FlairHdsLibs/FlairArdrone2'')
     99* ''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
    100100
    101101== Compile your own project ==
     
    103103__NOTE__: this is also works for projects provided in ''flair-src'' and ''flair-hds'' repositories.
    104104
     105You 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!
     106
     107The 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>''
     108{{{
     109$ mkdir -p $FLAIR_ROOT/flair-build/<mywork>/<myproject>
     110$ cd $FLAIR_ROOT/flair-build/<mywork>/<myproject>
     111$ $FLAIR_ROOT/flair-dev/scripts/cmake_codelite_outofsource.sh $FLAIR_ROOT/<path_to_my_project>
     112$ cd build
     113$ make install
     114}}}
     115
     116It will compile for x86_64 architecture. To compile for a different architecture, go to the corresponding directory, for example:
     117{{{
     118$ cd build_armv5te
     119or
     120$ cd build_armv7a_neon
     121or
     122$ cd build_cortexa7thf_neon_vfpv4
     123}}}
    105124
    106125== Compilation with debug (optional) ==