eg wrote:

Mikko Vainio wrote:

...

Dear boosters,

I'm trying to compile IOStreams from 1.38.0 with bzip2 compression enabled on windows. The docs say "you will need to set variables indicating the location of the source files". Setting boost.build variables in user-config.jam doesn't seem to do the trick. Providing "-s|BZIP2_SOURCE|=..." or any of the other related variables or combinations thereof on the command line for bjam does not help. Does anyone out there have an example on how to do this exactly? I suggest such an example to be added to the documentation. Or is this a bug in the build system?

While I haven't built it with 1.38.0, I have done previous versions.

I found that I ONLY set the zlib path environment variables... zlib_libpath, zlib_source, and zlib_include. In fact, I just set them as explicit environment variables and then called bjam with the correct toolset.

I did not do anything with no_zlib or no_compression (IIRC they caused me problems).

I believe the bzip2 settings are analogous.

Thanks, setting BZIP2_SOURCE and ZLIB_SOURCE as *environment* variables made it work. The IOStreams Installation documentation clearly says "..you may need to set several Boost.Build variables...", which is obviously misleading. Cheers, Mikko

eg wrote:

Mikko Vainio wrote:

...

Dear boosters,

I'm trying to compile IOStreams from 1.38.0 with bzip2 compression enabled on windows. The docs say "you will need to set variables indicating the location of the source files". Setting boost.build variables in user-config.jam doesn't seem to do the trick. Providing "-s|BZIP2_SOURCE|=..." or any of the other related variables or combinations thereof on the command line for bjam does not help. Does anyone out there have an example on how to do this exactly? I suggest such an example to be added to the documentation. Or is this a bug in the build system?

While I haven't built it with 1.38.0, I have done previous versions.

I found that I ONLY set the zlib path environment variables... zlib_libpath, zlib_source, and zlib_include. In fact, I just set them as explicit environment variables and then called bjam with the correct toolset.

I did not do anything with no_zlib or no_compression (IIRC they caused me problems).

I believe the bzip2 settings are analogous.

Thanks, setting BZIP2_SOURCE and ZLIB_SOURCE as *environment* variables made it work. The IOStreams Installation documentation clearly says "..you may need to set several Boost.Build variables...", which is obviously misleading. Cheers, Mikko