I would recommend the following steps for new users to create their
"own" buildconf:
1. Starting with the minimal package set from the tutorials
2. adapt it and adding needed packages for their system
3. create anywhere (fileserver/gitorious/github) the project and a
"buildconf" package
3.5. adapt if wished the bootstrap.sh
4. commit and push the adapted package set to the server
switch the current configuration to the new location
5. autoproj switch-config git <path-to-bootstrap.git>
These steps should do the job and regarding to the tutorial the most
intuitive.
Best,
Matthias
P.S. regarding Sylvains package_set suggestions, you have of course push
the package set to some location too and make it known in the manifest.
Post by Sylvain JoyeuxNot sure exactly what it is you are asking ...
If what you want is to create a "project" buildconf, i.e. the base
build configuration that all projects have for themselves, the best
way is definitely to start with the standard Rock buildconf (i.e. the
one you get when you bootstrap) since it gives you access to all the
rock packages, as well as already builds the toolchain.
If you want to create a package set, that is a different story. There
is an (undocumented) autoproj subcommand to create a new package set,
which can optionally contain already existing packages. It is
undocumented because not working properly in all cases. Anyways, what
one would do is
autoproj create-set package_set_name [package package package]
where
- the package_set_name is the name of the new package set, as well as
the directory in which the package set template is being created
- the packages are paths to packages already existing on disk
For instance, if you have created a bundle in bundles/test and want to
create a "shiny" package set, you would do
autoproj create-set shiny bundles/test
Of couse, autoproj create-set --help gives you this information
Sylvain
On Wed, Jul 2, 2014 at 6:23 PM, Carina Harrius <carina.harrius at dfki.de
Good evening,
I have a question concerning the setup of a new buildconf, i.e.
when I start creating a bundle for a new robot and need a
repository including a manifest file etc. to get started with. One
way of doing it would be to bootstrap an existing rock repository,
but this might not be the smartest way. As I need the information
for writing a new Rock tutorial, it would be great to be able to
describe the "best possible way" of getting started..can anyone
help me with that?
Thanks in advance and
best regards
Carina Harrius
_______________________________________________
Rock-dev mailing list
Rock-dev at dfki.de <mailto:Rock-dev at dfki.de>
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
_______________________________________________
Rock-dev mailing list
Rock-dev at dfki.de
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
--
Dipl.-Inf. Matthias Goldhoorn
Space and Underwater Robotic
Universit?t Bremen
FB 3 - Mathematik und Informatik
AG Robotik
Robert-Hooke-Stra?e 1
28359 Bremen, Germany
Zentrale: +49 421 178 45-6611
Besuchsadresse der Nebengesch?ftstelle:
Robert-Hooke-Stra?e 5
28359 Bremen, Germany
Tel.: +49 421 178 45-4193
Empfang: +49 421 178 45-6600
Fax: +49 421 178 45-4150
E-Mail: matthias.goldhoorn at informatik.uni-bremen.de
Weitere Informationen: http://www.informatik.uni-bremen.de/robotik
-------------- n?chster Teil --------------
Ein Dateianhang mit HTML-Daten wurde abgetrennt...
URL: http://www.dfki.de/pipermail/rock-dev/attachments/20140703/a1455c98/attachment.htm