
19 Feb
2006
19 Feb
'06
6:28 p.m.
"Jeff Garland"
Another possible idea. What if we created a new convention: <libname>_bcp.cfg that could be put in the library header directory. Then the library author could directly express the options using some trivial syntax of our own invention that would feed bcp and thus trivialize the command line for users. This syntax would be something like:
option option_name option_description bcp_command_parameters
We probably ought to be thinking about how this could work with Boost.Build. I don't see it clearly yet, but I bet there's some kind of integration opportunity. -- Dave Abrahams Boost Consulting www.boost-consulting.com