Purpose

While trying to use Buckminster for both my Java and C++ projects, I realized that Java projects within Eclipse were pretty straightforward but C/C++ projects were much more difficult to manage. As a result some new actors were proposed and then submitted to the Buckminster project. This example shows how to use these.

Why is it so hard to use Buckminster with non Java projects ?

Component materialization is much harder in non Java environments because :

there are no standard way to describe C/C++ projects so you have to write the CSpec file anyway ( contrary to Eclipse Java projects which provides a way to auto generate the CSpec )

Valid Properties

If the resource you are accessing is protected with basic authentication, you can also specify :

login : the login to use with basic authentication

pass : the password to use with basic authentication

Note that both properties have to be set to enable authentication.

options : a set of options to customize the fetch operation, valid options are :

uncompress : specify that the resource pointed by the url is an archive and that it should be uncompressed

flatten : valid only with uncompress. If specified the folder hierarchy is flatten

include : a regular expression to include specific files only. Note that you can specify multiple include directives in the options line. Regular expressions beginning with the '-' (minus sign) will be considered as an exclusion. See examples below :

Options samples

full options sample, uncompress the archive and flattens the folder hierarchy, including only files in the binaries directory that are not html files

uncompress;flatten;include=binaries/*;include=-*.html

flatten and include keywords will NOT work until the uncompress keyword is set, the following options line will simply copy the url resource locally.