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.