Developing a (nearly new) library possibly to be proposed for Boost
I'm revisiting https://svn.boost.org/trac/boost/wiki/StartModDev to try set up a new library. I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document. Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ? When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line git clone mailto:git@github.com:Beman/simple.git git@github.com:Beman/simple.git fails. This feels the right place for Or is recommended to use some folder like sandbox/libs/mylibrary/ for one's stuff, including of course a sandbox/libs/mylibrary/include/boost/mylibrary/ to hold my .hpp files? Either way I presume I need a link from modular-boost/boost to point to sandbox/libs/mylibrary/include/ Should I provide a symbolic link /D or a hardlink (as b2 headers creates)? C:\Windows\system32>mklink /D I:\modular-boost\boost\ mylibrary I:\sandbox\libs\ mylibrary \include\boost\ mylibrary symbolic link created for I:\modular-boost\boost\ mylibrary <<===>> I:\sandbox\libs\ mylibrary \include\boost\ mylibrary seems to work. Or do I add this folder to the Include directory list? (Tiresome) Suggestions? Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
On 09/02/14 19:05, Paul A. Bristow wrote:
I'm revisiting
https://svn.boost.org/trac/boost/wiki/StartModDev
to try set up a new library.
I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document.
Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ? When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line
git clone mailto:git@github.com:Beman/simple.git git@github.com:Beman/simple.git
cd $BOOST_ROOT cd libs git clone git@github.com:Beman/simple.git simple works fine for me, assuming there is no 'simple' directory that already exists.
Or do I add this folder to the Include directory list? (Tiresome)
A submodule is just a separate clone inside a tree, with the master tree aware of its revision. There is no problem putting a clone of any repository inside of boost/libs, and if the layout follows that of Boost, it (b2 headers, stage, install, etc) will just work. At least the headers work fine for boost.simple
On 2/9/2014 1:05 PM, Paul A. Bristow wrote:
I'm revisiting
https://svn.boost.org/trac/boost/wiki/StartModDev
to try set up a new library.
I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document.
Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ?
Yes.
When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line
git clone mailto:git@github.com:Beman/simple.git git@github.com:Beman/simple.git
fails.
Just cd to modular-boost's libs subdirectory, open a terminal, then git clone git@github.com:/simple.git
This feels the right place for
Or is recommended to use some folder like sandbox/libs/mylibrary/ for one's stuff, including of course a
sandbox/libs/mylibrary/include/boost/mylibrary/
to hold my .hpp files?
No.
Either way I presume I need a link from modular-boost/boost to point to sandbox/libs/mylibrary/include/
Should I provide a symbolic link /D or a hardlink (as b2 headers creates)?
Provide a symbolic link to the directory. From the modular-boost
C:\Windows\system32>mklink /D I:\modular-boost\boost\ mylibrary I:\sandbox\libs\ mylibrary \include\boost\ mylibrary symbolic link created for I:\modular-boost\boost\ mylibrary <<===>> I:\sandbox\libs\ mylibrary \include\boost\ mylibrary
seems to work.
Or do I add this folder to the Include directory list? (Tiresome)
Suggestions?
Paul
--- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 2/9/2014 1:05 PM, Paul A. Bristow wrote:
I'm revisiting
I hit the send button accidentally so please ignore my first reply.
to try set up a new library.
I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document.
Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ?
Yes.
When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line
git clone mailto:git@github.com:Beman/simple.git git@github.com:Beman/simple.git
fails.
Just cd to modular-boost's libs subdirectory, open a terminal, then git clone git@github.com:MyName/mylibrary.git or what I use since I avoid SSH on Windows: git clone https://github.com/MyName/mylibrary.git
This feels the right place for
Or is recommended to use some folder like sandbox/libs/mylibrary/ for one's stuff, including of course a
sandbox/libs/mylibrary/include/boost/mylibrary/
to hold my .hpp files?
Yes, but not in a sandbox but directly from the Boost libs/mylibrary folder.
Either way I presume I need a link from modular-boost/boost to point to sandbox/libs/mylibrary/include/
Should I provide a symbolic link /D or a hardlink (as b2 headers creates)?
Provide a symbolic link to the directory. From the modular-boost boost directory: mklink /d mylibrary ../libs/mylibrary/include/boost/mylibrary
C:\Windows\system32>mklink /D I:\modular-boost\boost\ mylibrary I:\sandbox\libs\ mylibrary \include\boost\ mylibrary symbolic link created for I:\modular-boost\boost\ mylibrary <<===>> I:\sandbox\libs\ mylibrary \include\boost\ mylibrary
seems to work.
Or do I add this folder to the Include directory list? (Tiresome)
No.
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: Sunday, February 09, 2014 9:25 PM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
to try set up a new library.
I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document.
Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ?
Yes.
As I surmised :-).
When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line
git clone git@github.com:Beman/simple.git
fails.
Just cd to modular-boost's libs subdirectory, open a terminal, then
git clone git@github.com:MyName/mylibrary.git
This doesn't work for me as I haven't got SSH set up right? I:\modular-boost\libs>git clone git@github:Beman/simple.git Cloning into 'simple'... ssh: connect to host github port 22: Bad file number fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
or what I use since I avoid SSH on Windows:
git clone https://github.com/MyName/mylibrary.git
This works OK, as I originally expected it to work using Tortoise GIT I:\modular-boost\libs>git clone https://github.com/Beman/simple.git Cloning into 'simple'... remote: Reusing existing pack: 12, done. remote: Total 12 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (12/12), done. Checking connectivity... done. BUT it doesn't for me as I expected using Tortoise GIT. There is no clone option :-( I had hoped to avoid the antediluvian command line ;-)
Provide a symbolic link to the directory. From the modular-boost boost directory:
mklink /d mylibrary ../libs/mylibrary/include/boost/mylibrary
OK - but is the /D option correct and why? /D creates a symbolic link, or a soft link. where b2 headers produces hard links (at present). Is this just a temporary 'feature'? Thanks for your helpful advices. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
This doesn't work for me as I haven't got SSH set up right?
I:\modular-boost\libs>git clone git@github:Beman/simple.git Cloning into 'simple'... ssh: connect to host github port 22: Bad file number fatal: Could not read from remote repository.
github -> github.com - Thomas
AMDG On 02/10/2014 09:34 AM, Paul A. Bristow wrote:
Provide a symbolic link to the directory. From the modular-boost boost directory:
mklink /d mylibrary ../libs/mylibrary/include/boost/mylibrary
OK - but is the /D option correct and why?
mklink /D creates a directory symlink. If this works, then b2 headers uses it. (You should see "- symlinks supported : yes" in the output)
/D creates a symbolic link, or a soft link.
where b2 headers produces hard links (at present).
Is this just a temporary 'feature'?
Thanks for your helpful advices.
In Christ, Steven Watanabe
On 2/10/2014 12:34 PM, Paul A. Bristow wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Edward Diener Sent: Sunday, February 09, 2014 9:25 PM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
to try set up a new library.
I've started by trying to use the simple 'library' I created over a year ago using a previous version of this document.
Is it intended that users should place their 'Boost-Wannabe' libraries in the modular-boost in /libs/mylibrary as other real Boost libraries ?
Yes.
As I surmised :-).
When I assumed this, I found it impossible to GIT clone my existing 'simple' library into the /libs folder as it is not empty, so the 2nd line
git clone git@github.com:Beman/simple.git
fails.
Just cd to modular-boost's libs subdirectory, open a terminal, then
git clone git@github.com:MyName/mylibrary.git
This doesn't work for me as I haven't got SSH set up right?
I:\modular-boost\libs>git clone git@github:Beman/simple.git Cloning into 'simple'... ssh: connect to host github port 22: Bad file number fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
SSH gives me a headache also, so I avoid it <g>.
or what I use since I avoid SSH on Windows:
git clone https://github.com/MyName/mylibrary.git
This works OK, as I originally expected it to work using Tortoise GIT
I:\modular-boost\libs>git clone https://github.com/Beman/simple.git Cloning into 'simple'... remote: Reusing existing pack: 12, done. remote: Total 12 (delta 0), reused 0 (delta 0) Unpacking objects: 100% (12/12), done. Checking connectivity... done.
BUT it doesn't for me as I expected using Tortoise GIT. There is no clone option :-(
I also use Tortoise GIT under Windows and when it can't do something I have to use the command line. It is not as polished as Tortoise SVN.
I had hoped to avoid the antediluvian command line ;-)
Provide a symbolic link to the directory. From the modular-boost boost directory:
mklink /d mylibrary ../libs/mylibrary/include/boost/mylibrary
OK - but is the /D option correct and why?
/D creates a symbolic link, or a soft link.
where b2 headers produces hard links (at present).
Is this just a temporary 'feature'?
I have already bored to death everybody on this mailing list by saying that 'b2 headers' should create symbolic links instead of hard links on Windows when the end-user has the administrative rights to do so. I believe Steve Watanabe is on top of this and if it is not working that way now it will be eventually.
Thanks for your helpful advices.
You are very welcome.
AMDG On 02/10/2014 10:30 AM, Edward Diener wrote:
I have already bored to death everybody on this mailing list by saying that 'b2 headers' should create symbolic links instead of hard links on Windows when the end-user has the administrative rights to do so. I believe Steve Watanabe is on top of this and if it is not working that way now it will be eventually.
It's done in develop. In Christ, Steven Watanabe
On 2/10/2014 1:46 PM, Steven Watanabe wrote:
AMDG
On 02/10/2014 10:30 AM, Edward Diener wrote:
I have already bored to death everybody on this mailing list by saying that 'b2 headers' should create symbolic links instead of hard links on Windows when the end-user has the administrative rights to do so. I believe Steve Watanabe is on top of this and if it is not working that way now it will be eventually.
It's done in develop.
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ? If I try 'mklink mylink bootstarp.log' I am successful so I definitely have rights to creating a symbolic file link.
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ?
Make sure you run: git submodule update
On 2/10/2014 7:52 PM, Thomas Suckow wrote:
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ?
Make sure you run: git submodule update
As I suspected it made no difference.
AMDG On 02/10/2014 04:48 PM, Edward Diener wrote:
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ?
If I try 'mklink mylink bootstarp.log' I am successful so I definitely have rights to creating a symbolic file link.
Does the output include: - symlinks supported : yes? If you look at tools/build/src/tools/link.jam:190 ff. it should test if $(.can-symlink) first, and then $(.can-hardlink). Is that the case? (https://github.com/boostorg/build/commit/3116da2b95ad02748c744a44ecec67789a9...) In Christ, Steven Watanabe
On 2/10/2014 10:55 PM, Steven Watanabe wrote:
AMDG
On 02/10/2014 04:48 PM, Edward Diener wrote:
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ?
If I try 'mklink mylink bootstarp.log' I am successful so I definitely have rights to creating a symbolic file link.
Does the output include: - symlinks supported : yes?
If you look at tools/build/src/tools/link.jam:190 ff. it should test if $(.can-symlink) first, and then $(.can-hardlink). Is that the case? (https://github.com/boostorg/build/commit/3116da2b95ad02748c744a44ecec67789a9...)
You are correct. It is working with the latest 'develop'. The error was mine.
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Tuesday, February 11, 2014 3:56 AM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
AMDG
On 02/10/2014 04:48 PM, Edward Diener wrote:
On Windows I checked out 'develop' at the modular-boost level and 'develop' at the Boost Build level. Then I re-ran .\bootstrap, deleted my current boost sub-directory, then re-ran .\b2 headers. The result is still hardlinks for individual files under the boost subdirectory. Did I miss something ?
If I try 'mklink mylink bootstarp.log' I am successful so I definitely have rights to creating a symbolic file link.
Does the output include: - symlinks supported : yes?
If you look at tools/build/src/tools/link.jam:190 ff. it should test if $(.can-symlink) first, and then $(.can-hardlink). Is that the case? (https://github.com/boostorg/build/commit/3116da2b95ad02748c744a44ecec67789a9...)
I'm doing something wrong and still not getting symlinks. I believe I have fumbled through the update and have this code in link.jam rule do-file-link { local target = [ path.native [ path.relative-to [ path.pwd ] $(<) ] ] ; local source = [ path.native [ path.relative-to [ path.pwd ] $(>) ] ] ; LOCATE on $(target) = . ; DEPENDS $(.current-target) : $(target) ; if $(.can-symlink) = true { link.mklink $(target) : $(source) ; } else if $(.can-hardlink) = true { DEPENDS $(target) : $(source) ; link.hardlink $(target) : $(source) ; } else { DEPENDS $(target) : $(source) ; common.copy $(target) : $(source) ; } } Using a administrator rights command window and this works OK. I:\modular-boost>mklink mylink bootstrap.log symbolic link created for mylink <<===>> bootstrap.log I:\modular-boost>.\bootstrap Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/boost-build2/doc/html/index.html I:\modular-boost>.\b2 headers Performing configuration checks - symlinks supported : no (cached) <<<<<<<<<<<<<<< :-( - junctions supported : yes (cached) - hardlinks supported : yes (cached) ...found 21781 targets... I've deleted /boost and rerun, but still creates hardlinks. What am I doing wrong? Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
AMDG On 02/11/2014 07:15 AM, Paul A. Bristow wrote:
<snip> I:\modular-boost>.\b2 headers
Performing configuration checks
- symlinks supported : no (cached) <<<<<<<<<<<<<<< :-( - junctions supported : yes (cached) - hardlinks supported : yes (cached) ...found 21781 targets...
I've deleted /boost and rerun, but still creates hardlinks.
What am I doing wrong?
bjam --help ... Important Options:
* ... * --reconfigure Rerun all configuration checks In Christ, Steven Watanabe
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Tuesday, February 11, 2014 4:37 PM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
AMDG
On 02/11/2014 07:15 AM, Paul A. Bristow wrote:
<snip> I:\modular-boost>.\b2 headers
Performing configuration checks
- symlinks supported : no (cached) <<<<<<<<<<<<<<< :-( - junctions supported : yes (cached) - hardlinks supported : yes (cached) ...found 21781 targets...
I've deleted /boost and rerun, but still creates hardlinks.
What am I doing wrong?
bjam --help ... Important Options:
* ... * --reconfigure Rerun all configuration checks
Ah. I:\modular-boost>b2 --reconfigure Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes <<<<<<<<<<<<<<<<<<< looks promising! - 32-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no - iconv (libc) : no - iconv (separate) : no - icu : no - icu (lib64) : no - message-compiler : yes - compiler-supports-ssse3 : yes - compiler-supports-avx2 : no - gcc visibility : no - long double support : yes warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. warning: No python installation configured and autoconfiguration note: failed. See http://www.boost.org/libs/python/doc/building.html note: for configuration instructions or pass --without-python to note: suppress this message and silently skip all Boost.Python targets - zlib : no (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - sync : building - system : building - test : building - thread : building - timer : building - wave : building ...patience... Well I'm not noted for *doing* patience but ... ;-) Thanks. Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Paul A. Bristow Sent: 11 February 2014 17:27 To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
AMDG
On 02/11/2014 07:15 AM, Paul A. Bristow wrote:
<snip> I:\modular-boost>.\b2 headers
Performing configuration checks
- symlinks supported : no (cached) <<<<<<<<<<<<<<< :-( - junctions supported : yes (cached) - hardlinks supported : yes (cached) ...found 21781 targets...
I've deleted /boost and rerun, but still creates hardlinks.
What am I doing wrong?
bjam --help ... Important Options:
* ... * --reconfigure Rerun all configuration checks
Ah. I:\modular-boost>b2 --reconfigure Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes <<<<<<<<<<<<<<<<<<< looks promising! [ ] And was successful, and works OK every time, But I can't get it to work on another machine. I've checked that the links.jam contains the new symlinks code. I've tried on develop and master branches. I've done b2 --reconfigure more than once. Is it significant that it says cached? Do I have to empty the cache? Any ideas what else I am doing wrong? Thanks Paul -- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
AMDG On 02/20/2014 10:16 AM, Paul A. Bristow wrote:
<snip>
I:\modular-boost>b2 --reconfigure Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes <<<<<<<<<<<<<<<<<<< looks promising! [ ] And was successful, and works OK every time,
But I can't get it to work on another machine.
I've checked that the links.jam contains the new symlinks code.
I've tried on develop and master branches.
The new code is only on develop.
I've done b2 --reconfigure more than once.
Is it significant that it says cached? Do I have to empty the cache?
That's what --reconfigure does.
Any ideas what else I am doing wrong?
Details please. a) Can you use mklink /D to create a symlink directly. b) What is the b2 output? c) How exactly does it fail? Does it think that it can't create symlinks? In Christ, Steven Watanabe
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Friday, February 21, 2014 3:29 PM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
AMDG
On 02/20/2014 10:16 AM, Paul A. Bristow wrote:
<snip>
I:\modular-boost>b2 --reconfigure Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes <<<<<<<<<<<<<<<<<<< looks promising! [ ] And was successful, and works OK every time,
But I can't get it to work on another machine.
I've checked that the links.jam contains the new symlinks code.
Details please.
a) Can you use mklink /D to create a symlink directly. b) What is the b2 output? c) How exactly does it fail? Does it think that it can't create symlinks?
Doh! Schoolboy error :-( To get symlinks, everything one does *must* have admin privileges. I was clicking on the wrong icon to get a command DOSBOX :-( To avoid potential confusion, I have now changed the admin one so that it is a different color :-) Thanks as usual. Paul PS Other may find is help to know that I have also (after a bit of time with my favourite search engine), for added convenience, edited the cmd.exe shortcut to that the Target: field is changed from just C:\Windows\System32\cmd.exe to C:\Windows\System32\cmd.exe /K "i: & cd .\modular-boost\" This changes partition from c: to I; and then cd to modular-boost. If one is working a particular library, say math, then adding \your-favorite-library might be good too? For example: C:\Windows\System32\cmd.exe /K "i: & cd .\modular-boost\math" If you just use c:\modular-boost, say, then it would be just C:\Windows\System32\cmd.exe /K "cd .\modular-boost\" HTH - but other tips and tricks welcome. --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
On 2/21/2014 1:35 PM, Paul A. Bristow wrote:
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Friday, February 21, 2014 3:29 PM To: boost@lists.boost.org Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
AMDG
On 02/20/2014 10:16 AM, Paul A. Bristow wrote:
<snip>
I:\modular-boost>b2 --reconfigure Building the Boost C++ Libraries. Performing configuration checks - symlinks supported : yes <<<<<<<<<<<<<<<<<<< looks promising! [ ] And was successful, and works OK every time,
But I can't get it to work on another machine.
I've checked that the links.jam contains the new symlinks code.
Details please.
a) Can you use mklink /D to create a symlink directly. b) What is the b2 output? c) How exactly does it fail? Does it think that it can't create symlinks?
Doh! Schoolboy error :-(
To get symlinks, everything one does *must* have admin privileges.
I was clicking on the wrong icon to get a command DOSBOX :-(
To avoid potential confusion, I have now changed the admin one so that it is a different color :-)
Thanks as usual.
Paul
PS Other may find is help to know that I have also (after a bit of time with my favourite search engine), for added convenience, edited the cmd.exe shortcut to that the Target: field is changed from just
C:\Windows\System32\cmd.exe
to
C:\Windows\System32\cmd.exe /K "i: & cd .\modular-boost\"
This changes partition from c: to I; and then cd to modular-boost.
If one is working a particular library, say math, then adding \your-favorite-library might be good too?
For example:
C:\Windows\System32\cmd.exe /K "i: & cd .\modular-boost\math"
If you just use c:\modular-boost, say, then it would be just
C:\Windows\System32\cmd.exe /K "cd .\modular-boost\"
HTH - but other tips and tricks welcome.
You can always change the "Start in:" box to set a starting directory for a command prompt in Windows.
participants (5)
-
Edward Diener -
Mathias Gaunard -
Paul A. Bristow -
Steven Watanabe -
Thomas Suckow