Dear all, My code uses some files from the boost sandbox repository as well as from boost. To be able tom compile my own code and stay up to date, I have downloaded and installed boost (svn, bjam) and downloaded the sandbox (svn). Now building boost was simple: create a build/ directory and call "bjam -a --toolset=gcc --build-dir=build --variant=release --link=shared --threading=multi --runtime-link=shared install" or something very similar In the sandbox things seem to be a bit differently. Using bjam in the same style as above does not work, in particular any "bjam ... install" comes back with a warning/notice notice: could not find main target install notice: assuming it is a name of file to create. don't know how to make <e>install ...found 1 target... ...can't find 1 target... and no files are installed (i.e. no files are copied to /usr/local/include). Is it possible to install the boost-sandbox files to /usr/local using bjam? Or is this not the way the sandbox should be used? many thanks Alle Meije Wink
Short follow-up ... Reading what I could find on the internet about this I saw that most people download boost, then download the sandbox, then copy or (perhaps better) link the sandboxes that they use to the boost tree. That's easy enough. Is this the intended use of the sandbox repositories though? If it is, why does it have bjam files? Thanks for shedding light on this. bw Alle Meije Fetching external item into 'gil/boost/gil/extension/io2/detail/platform_specifics.hpp' svn: warning: 'http://svn.boost.org/svn/boost/sandbox/gil/boost/gil/extension/io2/detail' is not the same repository as 'https://svn.boost.org/svn/boost' On 18 February 2011 13:25, Alle Meije Wink <a.m.wink@gmail.com> wrote: [...]
In the sandbox things seem to be a bit differently. Using bjam in the same style as above does not work, in particular any "bjam ... install" comes back with a warning/notice
notice: could not find main target install notice: assuming it is a name of file to create. don't know how to make <e>install ...found 1 target... ...can't find 1 target... [..]
On 2/21/2011 6:01 AM, Alle Meije Wink wrote:
Short follow-up ...
Reading what I could find on the internet about this I saw that most people download boost, then download the sandbox, then copy or (perhaps better) link the sandboxes that they use to the boost tree.
That's easy enough. Is this the intended use of the sandbox repositories though?
If it is, why does it have bjam files?
It has bjam files so you can run its tests and generate ( or regenerate ) its documentation. BTW, I hope you didn't download the entire sandbox using SVN. That's a huge amount of files. A possibly better way is to download only the top=level sandbox directly itself as a separate SVN checkout. Then download each library in which you are interested as a separate SVN checkout in a directory just below your local top-level sandbox directory. You can then update each library separately without having to worry about any of the others.
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of Edward Diener Sent: Tuesday, February 22, 2011 2:29 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] using the sandbox(es)
BTW, I hope you didn't download the entire sandbox using SVN. That's a huge amount of files. A possibly better way is to download only the top=level sandbox directly itself as a separate SVN checkout. Then download each library in which you are interested as a separate SVN checkout in a directory just below your local top-level sandbox directory. You can then update each library separately without having to worry about any of the others.
This is essential advice (I started to fall into this pit before I realised that I was making a big mistake). It could usefully be amplified too, for those not so familiar with Tortoise SVN. Can it be added to the docs please? Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com
That *is* good advice, thanks! And yes, I have checked out the whole repository... To be honest I didn't know that you could download a small part --will look it up in the docs! It did seem quite a lot, but nothing too shocking after checking out boost... With the smaller sub-repositories, my worry would be that you need to track down all the bits that are used by a particular part. In my case, what I want to use, variadic templates / containers, in turn include files from higher up the repository tree. Are these dependencies resolved when checking out (a la apt-get)? Best wishes Alle Meije
On 2/24/2011 4:58 AM, Alle Meije Wink wrote:
That *is* good advice, thanks!
And yes, I have checked out the whole repository... To be honest I didn't know that you could download a small part --will look it up in the docs!
It did seem quite a lot, but nothing too shocking after checking out boost... With the smaller sub-repositories, my worry would be that you need to track down all the bits that are used by a particular part.
In my case, what I want to use, variadic templates / containers, in turn include files from higher up the repository tree. Are these dependencies resolved when checking out (a la apt-get)?
No, the dependencies need to be resolved manually. Normally the docs will tell you if some sandbox library depends on another sandbox library.
Paul A. Bristow wrote:
This is essential advice (I started to fall into this pit before I realised that I was making a big mistake).
It could usefully be amplified too, for those not so familiar with Tortoise SVN.
Can it be added to the docs please?
Edward Diener wrote:
No, the dependencies need to be resolved manually.
Normally the docs will tell you if some sandbox library depends on another sandbox library.
Thanks for these helpful tips guys, hopefully this will be my last question about this -- I have been looking for ''The Docs'' on how to download a subset of the sandboxes (I've figured out which 3 I need). Browsing from one hopeful page to another I seam to alternate between https://svn.boost.org/trac/boost/wiki/BoostSubversion (which does not say anything about downloading anything other than everything) and https://svn.boost.org/trac/boost/wiki/BoostSandbox (which is not about downloading)... Do ''The Docs'' live somewhere else? Or are they for TortoiseSVN people only? Many thanks Alle Meije
On 2/24/2011 8:09 AM, Alle Meije Wink wrote:
Paul A. Bristow wrote:
This is essential advice (I started to fall into this pit before I realised that I was making a big mistake).
It could usefully be amplified too, for those not so familiar with Tortoise SVN.
Can it be added to the docs please?
Edward Diener wrote:
No, the dependencies need to be resolved manually.
Normally the docs will tell you if some sandbox library depends on another sandbox library.
Thanks for these helpful tips guys, hopefully this will be my last question about this --
I have been looking for ''The Docs'' on how to download a subset of the sandboxes (I've figured out which 3 I need). Browsing from one hopeful page to another I seam to alternate between https://svn.boost.org/trac/boost/wiki/BoostSubversion (which does not say anything about downloading anything other than everything)
It is really a subversion issue. From any subversion repository one can checkoout individual subversion folders, and one can instruct subversion if one wants subfolders of that folder or not when one checks out a subversion folder. This is just standard subversion functionality.
and https://svn.boost.org/trac/boost/wiki/BoostSandbox (which is not about downloading)...
Do ''The Docs'' live somewhere else? Or are they for TortoiseSVN people only?
TortoiseSVN is just a front-end for subversion under Windows. It is very good ( I use it ) but one can use command-line version if one wants instead.
participants (3)
-
Alle Meije Wink -
Edward Diener -
Paul A. Bristow