From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-09-24 04:25:17
Markus Schöpflin wrote:
> Vladimir Prus wrote:
>>did you worked this around already? If not, I have a very crude idea ---
>>definite kluge. Each toolset defines a rule called "C++-action", which
>>set ups build actions. You can tweak that rule for a given toolset, so
>>that it notices when the problematic file is compiled and changes
>>options appropriately. This *completely* bypasses all the build system
>>machinery, but per-source requirements can't be added to V1.
>>To determine when you're compiling problematic file, you can look at the
>>first argument of the rule. For example, you might be looking for
>>This is only an idea, not 100% finished recipe. Feel free to ask if you
>>run in any problems with it.
> Hmm, yes, this works. Not very nice but doable. Thanks, Volodya.
> I have been playing with the rule declare-local-target to define
> special build flags for a single object file but I had no luck.
Heh.. I was pretty sure I would have no luck, so resorted to kluges.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk