From: Daniel Wallin (daniel_at_[hidden])
Date: 2007-10-30 21:18:53
West, Larry wrote:
> On Sun Oct 28, 2007, David Abrahams wrote:
>>> Not using "cmd" wouldn't help with windows 260 char path limit,
>>> which seems like an unsolvable problem (short of reducing the
>>> features in the path, that is), or am I missing something?
>> That's true.
> The Windows 260-char path limit is for a given directory or file (and
> there are ways around this at the Win32 API level, but applications --
> such as compilers -- may not support the longer paths). That is, the
> total length of the directory path to any file (or directory) can't
> exceed 260 characters if you want to use it in general.
> But the doubly-quoted statement above mentioned "reducing features in
> the path", which makes me think the author was talking about the
> executable search path, i.e. the PATH environment variable.
I wasn't. With "features" I was referring to BB features that show up on
the path for a target. I probably should have said "properties".
-- Daniel Wallin Boost Consulting www.boost-consulting.com
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