Subject: Re: [boost] Developing a (nearly new) library possibly to be proposed for Boost
From: Edward Diener (eldiener_at_[hidden])
Date: 2014-02-10 13:30:17
On 2/10/2014 12:34 PM, Paul A. Bristow wrote:
>> -----Original Message-----
>> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Edward Diener
>> Sent: Sunday, February 09, 2014 9:25 PM
>> To: boost_at_[hidden]
>> 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 ?
> 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
>>> git clone git_at_[hidden]:Beman/simple.git
>> Just cd to modular-boost's libs subdirectory, open a terminal, then
>> git clone git_at_[hidden]: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_at_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
>> 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.