Gordan Sikic wrote:
Hi Arnaud,
could you point us (at least me) on the RPM specification file you used?
I didn't use any special rpm-spec file; it was generated during pacgkage
generation. In particular, I made following:
$ cmake-gui
(select CPACK option to make RPM)
$ make
$ make pack
Hi Arnaud,
could you point us (at least me) on the RPM specification file you used?
I didn't use any special rpm-spec file; it was generated during pacgkage
generation. In particular, I made following:
$ cmake-gui
(select CPACK option to make RPM)
$ make
$ make package
that's all.
For
Hi,
could you point us (at least me) on the RPM specification file you used?
For your information, I try to package Boost with CMake for Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=529563.
Do not hesitate if you would like to help :)
Best Regards
Denis
___
Hi,
(I consider myself user of both cmake and boost)
I'd like to report that I experienced problem while generating RPM
binary package on F11, and cmake 2.8.0; output of rpmbuild.err in RPM
build directory was as follows:
$cat rpmbuild.err
error: line 4: Tag takes single token only: Name: boos
Surya Kiran Gullapalli wrote:
One more thing I've observed is the Install target. The boost
include headers are installed in ${CMAKE_INSTALL_PREFIX}/include,
instead of ${CMAKE_INSTALL_DIRECTORY}/include/boost-1_41. I'm using
cmake for my project and cmake checks for
include/b
Vladimir Prus wrote:
troy d. straszheim wrote:
Surya Kiran Gullapalli wrote:
I'll have a look. Meanwhile, could you try specifying the paths
with
forwardslashes rather than backslashes?
Thanks, It worked
This behaviour is different from bjam.
I'm not too concerned with doing things exactl
troy d. straszheim wrote:
> Surya Kiran Gullapalli wrote:
>>> I'll have a look. Meanwhile, could you try specifying the paths
>>> with
>> forwardslashes rather than backslashes?
>>
>> Thanks, It worked
>>
>> This behaviour is different from bjam.
>
> I'm not too concerned with doing things exa
Surya Kiran Gullapalli wrote:
I'll have a look. Meanwhile, could you try specifying the paths
with
forwardslashes rather than backslashes?
Thanks, It worked
This behaviour is different from bjam.
I'm not too concerned with doing things exactly as bjam does them.
In the case of zlib/bzip2, w
>
> One more thing I've observed is the Install target. The boost include
> headers are installed in ${CMAKE_INSTALL_PREFIX}/include, instead of
> ${CMAKE_INSTALL_DIRECTORY}/include/boost-1_41. I'm using cmake for my
> project and cmake checks for include/boost-1_41/boost/version.hpp file (I'm
> us
> I'll have a look. Meanwhile, could you try specifying the paths with
forwardslashes rather than backslashes?
Thanks,
It worked
This behaviour is different from bjam. If ZLIB_INCLUDE_DIR is not defined
and ZLIB_SOURCE is defined, bjam builds a zlib library automatically with
boost prefix. Same
Surya Kiran Gullapalli wrote:
Platform: Windows.
Compiler: MSVC 8.0 SP1
Boost.Cmake unable to configure iostreams with zlib (or bzip2). I've
ZLIB_SOURCE env variable set to the location of zlib source code.
I've also set ZLIB_INCLUDE_DIR and ZLIB_LIB_DIR in cmake-gui but it is
not working. I
Platform: Windows.
Compiler: MSVC 8.0 SP1
Boost.Cmake unable to configure iostreams with zlib (or bzip2). I've
ZLIB_SOURCE env variable set to the location of zlib source code.
I've also set ZLIB_INCLUDE_DIR and ZLIB_LIB_DIR in cmake-gui but it is not
working. I'm getting the following errors. Th
On Nov 18, 2009, at 12:53 PM, troy d. straszheim wrote:
> James C. Sutherland wrote:
>> On Nov 18, 2009, at 12:25 PM, troy d. straszheim wrote:
>>> James C. Sutherland wrote:
On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
> Here's the first release for 1.41.0, take it out for a s
James C. Sutherland wrote:
On Nov 18, 2009, at 12:25 PM, troy d. straszheim wrote:
James C. Sutherland wrote:
On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
Here's the first release for 1.41.0, take it out for a spin:
http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
Get back t
James C. Sutherland wrote:
On Nov 18, 2009, at 12:25 PM, troy d. straszheim wrote:
James C. Sutherland wrote:
On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
Here's the first release for 1.41.0, take it out for a spin:
http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
Get back t
On Nov 18, 2009, at 12:25 PM, troy d. straszheim wrote:
> James C. Sutherland wrote:
>> On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
>>> Here's the first release for 1.41.0, take it out for a spin:
>>>
>>> http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
>>>
>>> Get back to me h
James C. Sutherland wrote:
On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
Here's the first release for 1.41.0, take it out for a spin:
http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
Get back to me here with your comments or questions.
-t
Why is boost::mpi "disabled" on app
On Nov 18, 2009, at 9:56 AM, troy d. straszheim wrote:
>
> Here's the first release for 1.41.0, take it out for a spin:
>
> http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
>
> Get back to me here with your comments or questions.
>
> -t
>
Why is boost::mpi "disabled" on apple?
The bj
> Here's the first release for 1.41.0, take it out for a spin:
>
> http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
>
> Get back to me here with your comments or questions.
Looks good here. All my tests pass on Darwin. Will be trying on FreeBSD but
don't expect results from that for a
Here's the first release for 1.41.0, take it out for a spin:
http://sodium.resophonic.com/boost-cmake/1.41.0.cmake0
Get back to me here with your comments or questions.
-t
___
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boo
20 matches
Mail list logo
