"Pablo Aguilar" <pablo.aguilar@gmail.com> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:ubr6xn553.fsf@boost-consulting.com...
"Pablo Aguilar" <pablo.aguilar@gmail.com> writes: [snip]
Ok, I won't argue, as not parsing them would make my life a whole lot easier. I do suggest you take a look at John Torjo's utility though, if I got it correctly, it doesn't parse the .jam files but rather just adds the requested threading/linkage/debug options to the bjam command line.
Okay, I can look at it (again; saw it some time ago), but to what end? Is there some way I can help you once I've seen it?
Yes, thank you... What I'd like to know is if that's a viable option for selecting which targets to build from within a GUI tool. That is, if a jamfile for a given project already has, for example, threading options; will specifying threading at the command line to bjam, create ONLY the what was requested?
Rephrasing a little, will the options specified at the CL override or add to those specified in the jamfile? And if it's an override, will that be enough for me to specify build targets without parsing jam files?
Oh, I can answer that without downloading John's tool. There are two kinds of options in Jamfiles: those that specify target requirements (i.e. "needs multithreading" or "needs the FOO preprocessor symbol defined") and those that specify the "default BUILD" (that is, "if not otherwise specified, link to the static runtime library"). The first kind, requirements, can't be overridden at the command-line. The other kind can. HTH, -- Dave Abrahams Boost Consulting www.boost-consulting.com