Subject: Re: [Boost-build] Boost-build Digest, Vol 84, Issue 38
From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2012-08-30 12:22:23
> OK, thanks for the info. I will have to "roll my own" patch, as our
> build automation is changing and drive letters will not be an option
> for shares.
> Do you have any thoughts as to areas that will require changes? Our
> specific use for UNC paths will be for third party libraries.
Sorry but I honestly do not know yet. I'll let you know as I manage
to get my head wrapped around all the path usage I'm currently
researching in Boost Build/Jam.
I know Boost Jam as its internal path handling (e.g.
pathsys.c/pathnt.h/pathunix.h modules and their path_as_key() function
used to get a key used to identify file system objects in different
Boost Jam & Build mappings, INCLUDE statement, NORMALIZE_PATH builtin
rule) and Boost Build has its own (e.g. path features, import builtin &
> I am planning to use a call to regexec() near the beginning of
> builtin_normalize_path() to detect a UNC path and trigger different
> behavior in the rest of the function. Do you think this would
> significantly affect performance? I think this may be a good regex:
And again - I really can not say up front. But feel free to try and
hack it together. And if you get something working in your scenario - I
hope you send it back in.
Also, if possible, try to add tests for the features you need in
Boost Build project's test folder.
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