Christoph Duelli wrote:
Vladimir Prus wrote:
Christoph Duelli wrote:
bjam has the option --build-type=complete
Is it somehow possible (other than manually editing the Makefile) to specify this option when calling configure?
(I'm asking because I'd like to script the build of Boost; and so far it only builds in release mode. I'd like to avoid to edit Makefile on any machine I need to build Boost on.)
Out of curiousity -- why do you want to use configure, as opposed to invoking 'bjam' directly? The only two things that are really being auto-configured are python and ICU -- do you actually need to auto-configure those? Well, it's not exactly that I want to use configure. But configure is right there when you un-tar the boost .bz2 package. So it suggested itself. (Whereas bjam is either an extra package to install or else it is hidden inside some subdirectory of boost.) Boils down to: Reason 1) usual way is: ./configure; make Reason 2) here: less work than looking for bjam, checking what arguments (if any) to pass (If configure is not the recommended way to build boost, why is it there at all?)
Basically, "configure/make" did simplify things for certain use-cases, at the cost of confusing users who expect this is "standard" configure. I'm planning to propose a differently named solution, but first I'm trying to figure why 'configure/make' is used now, to confirm my theory. - Volodya