Am 12.03.2013 12:58, schrieb Stefan Herbrechtsmeier:
Am 12.03.2013 11:48, schrieb Koen Kooi:
Op 12 mrt. 2013, om 11:19 heeft Stefan Herbrechtsmeier
het volgende geschreven:
Am 12.03.2013 00:44, schrieb Saul Wold:
On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
The current boost recip
Am 12.03.2013 11:48, schrieb Koen Kooi:
Op 12 mrt. 2013, om 11:19 heeft Stefan Herbrechtsmeier
het volgende geschreven:
Am 12.03.2013 00:44, schrieb Saul Wold:
On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
The current boost recipe only creates the bjam build tool during
a native run
Op 12 mrt. 2013, om 11:19 heeft Stefan Herbrechtsmeier
het volgende geschreven:
> Am 12.03.2013 00:44, schrieb Saul Wold:
>> On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
>>> The current boost recipe only creates the bjam build tool during
>>> a native run and thereby is not usable for
Am 12.03.2013 00:44, schrieb Saul Wold:
On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
The current boost recipe only creates the bjam build tool during
a native run and thereby is not usable for other native programs
that depend on a boost library. Split out the build tool into its
own bj
On 03/07/2013 08:37 AM, Stefan Herbrechtsmeier wrote:
The current boost recipe only creates the bjam build tool during
a native run and thereby is not usable for other native programs
that depend on a boost library. Split out the build tool into its
own bjam recipe and add real native support to
The current boost recipe only creates the bjam build tool during
a native run and thereby is not usable for other native programs
that depend on a boost library. Split out the build tool into its
own bjam recipe and add real native support to the boost recipe.
This allows recipes to depend on nativ
