From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-09-08 15:37:23
Andrey Melnikov wrote:
>>>One note: INCLUDE and LIB should be set too because the order of
>>>directories is important in this case.
> Why? <include> just adds new folders to the end of search path. Is this
> bad? How this can cause problems? I don't see differences between
> INCLUDE and -I
All '<include>' are passed through property list which is sorted
(alphabetically I guess). Sorting breaks order of include directories
which can be fatal in case of MSVC + MS PSDK configuration.
The same is true for LIB and PATH.
> Such problems will be easily seen during even basic smoke tests. Also we
> don't use and don't support neither win32.mak nor .Net MC++.
> If we don't see problems, why to overengineer the startup code?
> Switching to this new approach with <include> can actually *save* us
> some work because we are implementing psdk this way anyways.
> We change the toolset a lot. We'll test it on all supported platforms
> anyways. So at this point we can afford it.
> When psdk is done, the only things we should add to support the rest of
> the versions are several search path constants for each version.
OK. Your words sound more convincing then mine. :-)
Best regards/Venlig hilsen,
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