Changes between Initial Version and Version 1 of WikiStart/Toolchain/NewPackages


Ignore:
Timestamp:
08/29/11 14:59:08 (8 years ago)
Author:
sylvain.joyeux
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart/Toolchain/NewPackages

    v1 v1  
     1This covers the addition of new packages in Rock 
     2 
     3== New packages == 
     4 
     5To be added to rock, a new package should: 
     6 
     7 * have been reviewed for sanity (it does not necessarily have to be perfect, it just has to be good enough). This should be done by sending an announcement on rock-dev and get some comments 
     8 * have been reviewed for licensing ("viral" licenses, ...) 
     9 
     10 * packages that are meant to go into rock.base or rock.toolchain will have higher quality requirements. 
     11 
     12== Adding the package == 
     13 
     14 * add the new package to the autobuild file in rock/. Libraries go into libs.autobuild and oroGen packages to orogen.autobuild 
     15 * add them TO THE TOPLEVEL. They should NOT be in an in_flavor block. Obviously, a new package cannot be in next or stable. 
     16 * check if the import works for you: once you have added the package, doing "autoproj update my/new/package" should not fail 
     17 * check if the build works for you: my/new/package and do "autoproj build my/new/package". This should not fail.