$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-header.inc")
?>
- Next message: Rene Rivera: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
- Previous message: David Abrahams: "Re: [Boost-build] [newbie] Building Boost with STLport without iostreams."
- In reply to: Vladimir Prus: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
- Next in thread: Rene Rivera: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
Vladimir Prus wrote:
> On a second though, it looks like 'can-build' returning false make
> generator fail during find-viable-generators call, instead of failing
> in 'run' method. So, it's a mechanism for making generator fail
> earlier. I'm not sure if we need this second mechanism, given that
> 'run' can return nothing already.
If that's true, then why did you initially use the "generate-targets"
rule instead of the "run" rule to implement the link-runtime=static
restriction?
--
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
- Next message: Rene Rivera: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
- Previous message: David Abrahams: "Re: [Boost-build] [newbie] Building Boost with STLport without iostreams."
- In reply to: Vladimir Prus: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
- Next in thread: Rene Rivera: "Re: [Boost-build] CVS: boost/tools/build/v2/build generators.jam, 1.100, 1.101 targets.jam, 1.197, 1.198"
$include_dir="/home/hyper-archives/boost-build/include";
include("$include_dir/msg-footer.inc");
?>