doc/guide/src/customization.page in autoproj-1.4.3 vs doc/guide/src/customization.page in autoproj-1.4.4

- old
+ new

@@ -9,12 +9,11 @@ The <tt>layout</tt> section of <tt>autoproj/manifest</tt> offers two things: * select which packages/package sets to build and * build packages in specific subdirectories This section lists packages or package sets that ought to be built by autoproj. -For instance, in the following example, only the <tt>orocos/rtt</tt> and -<tt>orocos/ocl</tt> +For instance, in the following example, only the <tt>orocos/rtt</tt> and <tt>orocos/ocl</tt> packages of the rubim.orocos source will be built. The other will be excluded from the build. {coderay:: yaml} package_sets: @@ -44,11 +43,11 @@ {coderay} Configuration files like <tt>autoproj/manifest</tt> are YAML file. As such, they aresensible to indentation. The snippet above should be read as: in the layout, there is first a "lib" part and second the packages whose names start with "orocos/" _(first level of indentation)_. In the "lib" part, the packages are "typelib", "utilmm" and "utilrb" _(second level of indentation)_. -{.warning} +{: .warning} Alternatively, the example above could be written: {coderay:: yaml} layout: - lib: [typelib, utilmm, utilrb] @@ -57,11 +56,11 @@ Finally, names of sublayouts can be used as arguments in the autoproj command line, instead of package names: autoproj build lib -{.commandline} +{: .commandline} Removing packages from the build -------------------------------- Instead of having to list all packages that you do want to build, it is possible to list the packages that you don't want to build. Simply list them in the @@ -119,11 +118,11 @@ Building local packages ----------------------- You can list local packages that are not in an imported package set by placing the definitions in autoproj/, in a file ending with <tt>.autobuild</tt>. See [this -page](source_yml.html) for information on how to write autobuild files. +page](package_sets/autobuild.html) for information on how to write autobuild files. Setting up the path to specific commands (make, parallel builds) ---------------------------------------------------------------- The autobuild API allows to specify what specific installed command to use for @@ -176,20 +175,14 @@ {coderay} If the command line is autoproj build modules/logger -{.cmdline} +{: .cmdline} -then only modules/logger and modules/base will be built -- assuming -modules/logger depends on modules/base -- but typelib will be left alone -_regardless of its state_. It may speed up the build process tremendously, but -also may generate errors if other packages needed to be updated. +then modules/logger and its dependencies will be built. Idem, if the command line is: -Idem, if the command line is: - autoproj build asguard -{.cmdline} +{: .cmdline} -then all packages or asguard/ are built _but none of the dependencies that are -defined in other places in the layout_. +then all packages or asguard/ are built, including their dependencies