[Rock-dev] about AUTOPROJ_PROJECT_BASE and code

[Sylvain Joyeux]

On 06/08/2011 01:50 PM, Thomas Roehr wrote:
>>> To be able to specialize configurations (relies on the underscore as
>>> separator):
>>> std::string filename =
>>> utilmm::ConfigurationFinder::findSystemConfig("package-name", crex_0);
>>>
>>> Searches
>>> first in $ROCK_CONFIG_PATH/configuration/package-name/crex/0/
>>> and falls back to $ROCK_CONFIG_PATH/configuration/package-name/crex/
>>>
>>> Similar for ruby.
>> What happens if ROCK_CONFIG_PATH is not set ? The issue is that 
>> orogen components SHALL be able to build even if ROCK_CONFIG_PATH is 
>> not set. However, I personally feel that the config search
>
> The build is completly independant of ROCK_CONFIG_PATH. It is a 
> runtime issue, i.e. if it is not set it depends mainly on the 
> component to handle this. However, the current implementation only 
> prints a warning to stderr, when ROCK_CONFIG_PATH is not set, and 
> searches in the local folder. Otherwise, it might be better to just 
> throw an exception.
That's my problem. From a library design point of view, it might be 
better to throw an exception. From a component point of view, if it is 
used for default values, then the best behaviour is just to ignore ...

Sylvain