On Mon, May 23, 2011 at 1:52 PM, Lars Viklund wrote:

On Mon, May 23, 2011 at 09:01:15AM +0200, Ovanes Markarian wrote:

...

Hi Vikash,

please use BCP tool to extract the needed libs: http://www.boost.org/doc/libs/1_46_1/tools/bcp/doc/html/index.html

On Mon, May 23, 2011 at 7:31 AM, vikash sharma

...

Hi,

Could anyone please help me out. I need boost header only libraries for boost shared pointer and boost foreach. But i am not able to find the header libraries available for download any where on the boost website. I remember seeing the header only libraries some time back. But right now dont see the header only libraries for any of the boost versions released till date.

Hello (and do not top-post).

If you just need the headers, just copy/use the boost/ directory of the releases.

BCP is a nice tool in theory, but doesn't do the extraction correctly for some of the libraries.

It _might_ work for you, but be aware that it tends to fail horribly on anything that uses the preprocessor. It has failed miserably on MPL for some.

Sorry for top-posting... Forgot it.. But anyway, copying the directory might fail as well, just because this particular header lib might depend on other libs. In that case you will need to strip the dependencies manually. With Kind Regards, Ovanes

On Mon, May 23, 2011 at 9:09 PM, Lars Viklund wrote:

On Mon, May 23, 2011 at 07:02:45PM +0200, Ovanes Markarian wrote:

...

On Mon, May 23, 2011 at 1:52 PM, Lars Viklund wrote:

[...]

You read me wrong. I said to copy the boost/ directory as a whole.

Then of course, if you feel brave, you can always remove libraries that you know it will not depend on.

Personally, I do not see the need to extract single libraries, as the cost (hours/days of work, which may blow up) way outweighs the benefits (what, saving a couple of megs of disk space?).

Lars, It is not the matter of saving some megs. It can easily happen, that you need to implement some tooling where boost would be extremely helpful. But you are unable to reference some existing boost lib distro in the enterprise repository, because it is not there. It is also not possible to put boost libs within some short term into the common libs repository, since there might be some evaluation processes when a lib is allowed to be a part of common repository. On the other hand the tool to be developed is so small (a couple of files) that you still don't want to put into the tools repo the whole boost headers. What do you think how many header files are in the boost header directory? In the 1.45 there are over 7500 files. In that case it means, that your user will need to check-out over 7500 files to build some tiny tool. Do you really want the users of that tiny project to be required to check out with your 20 source files about 7500 files, and that only because you just wanted shared pointer or some other small lib form boost? It might be hard to understand but there are some enterprise policies in big companies and there is no way to just to overcome them. Best Regards, Ovanes

I created a "boostvault" folder and just renamed the includes in the header only lib files. One lib is actual copied boostvault, the other is from newer version of boost. We use multiple versions of boost already. Of course you must handle any dependency issues to "boost" this way. Doing it this way makes it maintainable (can see difference from 'boost' normal lib and 'boostvault' manual header only). Regards Rune On Mon, May 23, 2011 at 10:21 PM, Ovanes Markarian wrote:

On Mon, May 23, 2011 at 10:16 PM, Ovanes Markarian wrote:

...

On Mon, May 23, 2011 at 9:09 PM, Lars Viklund wrote:

...

On Mon, May 23, 2011 at 07:02:45PM +0200, Ovanes Markarian wrote:

...

On Mon, May 23, 2011 at 1:52 PM, Lars Viklund wrote:

[...]

You read me wrong. I said to copy the boost/ directory as a whole.

Then of course, if you feel brave, you can always remove libraries that you know it will not depend on.

Personally, I do not see the need to extract single libraries, as the cost (hours/days of work, which may blow up) way outweighs the benefits (what, saving a couple of megs of disk space?).

Lars, It is not the matter of saving some megs. It can easily happen, that you need to implement some tooling where boost would be extremely helpful. But you are unable to reference some existing boost lib distro in the enterprise repository, because it is not there. It is also not possible to put boost libs within some short term into the common libs repository, since there might be some evaluation processes when a lib is allowed to be a part of common repository. On the other hand the tool to be developed is so small (a couple of files) that you still don't want to put into the tools repo the whole boost headers. What do you think how many header files are in the boost header directory? In the 1.45 there are over 7500 files. In that case it means, that your user will need to check-out over 7500 files to build some tiny tool. Do you really want the users of that tiny project to be required to check out with your 20 source files about 7500 files, and that only because you just wanted shared pointer or some other small lib form boost? It might be hard to understand but there are some enterprise policies in big companies and there is no way to just to overcome them.

And also  some small addition: It might happen that the enterprise wide common repo contains boost, but the version, which does not feature the desired lib. What do you do then? Switching the boost version must be tested within all dependent projects. This is not that trivial. I understand, that in ideal world a boost lib distro is just updated as soon as it is out, but it might be not the case for various reasons.

Regards, Ovanes

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users