|
|
This is a little cart-before-the-horse, as you would need to be able to use the option system before/when you're actually loading the options.
I guess it might be possible, so long as you specify -in:path on the command line before you specify the options file (so "antibody_designer.linuxclangrelease -in:path antibody_designer @flags" might be workable, "antibody_designer.linuxclangrelease @flags -in:path antibody_designer" wouldn't be, at least without changing options loading semantics.)
To make the first case work, you'd probably have to alter OptionCollection::load_option_from_file() in src/utility/options/OptionCollection.cc to specifically introspect the -in:path option and uses those paths as fallbacks. The general -in:path loading mechanism that usually happens through izstream won't work, as that doesn't get set until the options loading is finished. |
|