Boost C++ Libraries: Ticket #1816: --build-type=complete broken in current svn

Vladimir Prus — Fri, 11 Apr 2008 17:16:07 GMT

Do you mean this issue happens only with --build-type=complete?

Fri, 11 Apr 2008 17:25:50 GMT

I can't say 'only' since I have only tested 3 cases:

1) Don't specify anything, I get MT 2) specify threading=single -> OK 3) --build-type=complete -> error

anonymous — Mon, 28 Apr 2008 18:21:37 GMT

remove the -sICU_PATH and it will probably work... EXPAT_LIBPATH and _INCLUDE have to specified as env-variables, not as bjam variables as it seems...

status changed; resolution set

Vladimir Prus — Fri, 09 May 2008 08:03:36 GMT

status new → closed
resolution → fixed

(In [45245]) Don't assign build properties as target's usage requirements when it fails to generate.

We try to avoid building the same target twice, by caching the result of previous calls to target.generate, and returning it if a build request with the same property set is made. When the target fails to generate, for example due to <build>no property, we used to store the entire build property set as the usage requirements of the build. This is clearly, wrong, this patch makes us store <build>no as usage requirements instead.

Fixes #1816.