From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2006-03-27 04:42:48
Rene Rivera wrote:
> Not of little help, since it's the common use case to target the
> platform one is running on. Although Cygwin is a special case. But then
> again it should be handled differently than plain Win32/NT.
Sorry this should have read: Of little help for what I have in mind,
i.e. deducing which platform the build is intended to go.
>> Would it be possible to get this platform information in bjam too?
> I don't understand that question. Get which platform information? And is
> that in bjam or Boost.Build?
Never nor. I am speaking about the config.hpp headers of the boost library.
But as I am just recognizing also the config.hpp does not give such
information in the form of a macro definition. It just defines
BOOST_PLATFORM to some platform dependent string. e.g.
#define BOOST_PLATFORM "Cygwin".
What I was hoping for is something like
if compiling for cygwin.
So perhaps the best I can do is rethinking my problem and try to
approach from a different angle.
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