This is a re-post from the boost-users list, Thanks to Troy d.
straszheim who reminded me there that there's a dedicated list here.
I used CMake to build boost 1.39 and found at least two problems:
- In the cmakelist.txt file the BOO
Tan, Tom (Shanghai) wrote:
> This is a re-post from the boost-users list, Thanks to Troy d.
> straszheim who reminded me there that there's a dedicated list here.
>
>
>
> I used CMake to build boost 1.39 and found at least two problem
On Tue, May 12, 2009 at 5:11 PM, Brad King wrote:
> Beman Dawes wrote:
>>
>> On Tue, May 12, 2009 at 4:38 PM, Doug Gregor
>> wrote:
>>
>>> Beman, did you enable testing?
>>
>> No. I figured that was a bit much for now.
>>
>>> Even without all of the tests, Boost still has a huge number of targets
>You are wrong. You can either add:
>
> define=_BIND_TO_CURRENT_VCLIBS_VERSION
>
>to command line or edit Jamroot to set a define for all of Boost.
>
>- Volodya
Thanks, very nice to learn this trick.
___
Boost-cmake mailing list
Boost-cmake@lists.b
On Wed, May 13, 2009 at 12:02 AM, Doug Gregor wrote:
> Thanks! I committed some changes to the release branch that will, I
> think, work around this problem. It looks like "foreach" is a special
> variable in NSIS, and we have a library named "foreach", which appears
> to have caused the failure.
Tan, Tom (Shanghai) wrote:
This is a re-post from the boost-users list, Thanks to Troy d.
straszheim who reminded me there that there’s a dedicated list here.
Good to see you over here
I used CMake to build boost 1.39 and found
See http://boost.cowic.de/rc/Boost-1.40.0-vc9.exe
I've tried this installer on a Windows 7 machine and it worked without
problems. Haven't actually tried to use any of the libraries.
The most striking aspect of this exercise was how smooth the process
is from the release manager's perspective. I
Beman Dawes wrote:
For me the next step will be to read the CMake docs a bit, look
through the CMake files in the Boost tree, and generally become more
familiar with CMake as it applies to Boost.
Hey,
This might be easiest: if you have edits, click "show source" on the
right hand side of t
2009/5/13 troy d. straszheim :
> Tan, Tom (Shanghai) wrote:
>>
>> I used CMake to build boost 1.39 and found at least two problems:
>>
>> - In the cmakelist.txt file the BOOST_VERSION_MINOR is 38, instead of 39
>>
>
> A known problem. You can tweak this in the toplevel CMakeLists.txt.
I've added
There's a git branch of patches to the 1.39 release of cmake here:
http://sodium.resophonic.com/git/boost_patches/?h=cmake-patches/Boost_1_39_0
If we're going to do a patch release of 1.39 for the boost.build tweaks,
I'd like to get these in as well. Tarballs of this patchset from this
git re
On Wed, May 13, 2009 at 6:33 AM, Beman Dawes wrote:
> On Wed, May 13, 2009 at 12:02 AM, Doug Gregor wrote:
>> Thanks! I committed some changes to the release branch that will, I
>> think, work around this problem. It looks like "foreach" is a special
>> variable in NSIS, and we have a library nam
On Wed, May 13, 2009 at 5:37 AM, Beman Dawes wrote:
> On Tue, May 12, 2009 at 5:11 PM, Brad King wrote:
>> Beman Dawes wrote:
>>>
>>> On Tue, May 12, 2009 at 4:38 PM, Doug Gregor
>>> wrote:
>>>
Beman, did you enable testing?
>>>
>>> No. I figured that was a bit much for now.
>>>
Even w
On Wed, May 13, 2009 at 6:41 AM, troy d. straszheim wrote:
> Tan, Tom (Shanghai) wrote:
>>
>> This is a re-post from the boost-users list, Thanks to Troy d. straszheim
>> who reminded me there that there’s a dedicated list here.
>>
>
> Good to see you over here
>
>> --
On Wed, May 13, 2009 at 9:51 AM, Daniel James wrote:
> 2009/5/13 troy d. straszheim :
>> Tan, Tom (Shanghai) wrote:
>>>
>>> I used CMake to build boost 1.39 and found at least two problems:
>>>
>>> - In the cmakelist.txt file the BOOST_VERSION_MINOR is 38, instead of 39
>>>
>>
>> A known problem.
Doug Gregor wrote:
Basically, when you have both a shared and a static library "foo" in
the same directory, CMake uses -lfoo and we'll pick up whatever the
linker wants (the shared library).
[snip]
Other ideas for a fix to this problem would be helpful! I'm stumped.
CMake 2.6 uses full paths
git clone git://sodium.resophonic.com/boost_cookbook
cd boost_cookbook
checkout -b my_doctweaks_branch boost_cmake_docs
emacs source/*.rst
When I try this on Windows, I get:
--
c:\opt>git clone sodium.resophonic.com/boost_cookbook
fatal: Could not switch to 'sodium.resophonic.com'
c:\o
David Wolfe wrote:
This is my first attempt to use git, so I have no idea what this means.
Did that branch disappear or something?
Sorry about that. Docs fixed.
-t
___
Boost-cmake mailing list
Boost-cmake@lists.boost.org
http://lists.boost.org/ma
The Windows installer created a directory tree like this:
Program Files
Boost
bin
...
include
boost-1_40
boost
...
lib
..
I'm uncomfortable with that.
It is different from the directory structure
x86 on what platform? I was planning to build x86 binaries for Mac OS
10.4 and 10.5. We might be able to prod someone into building x86
Windows binaries. Any takers?
I'll take a stab at this if someone can help me get started. Should I
do:
svn co http://svn.boost.org/svn/boost/trunk boost-tr
>> I used CMake to build boost 1.39 and found at least two problems:
>> - In the cmakelist.txt file the BOOST_VERSION_MINOR is 38, instead
of 39
>>
>A known problem. You can tweak this in the toplevel CMakeLists.txt.
Look for BOOST_VERSION_MINOR.
That's what I did when I first saw it, seems
On Wed, May 13, 2009 at 7:27 PM, Tan, Tom (Shanghai) wrote:
>>> I used CMake to build boost 1.39 and found at least two problems:
>>> - In the cmakelist.txt file the BOOST_VERSION_MINOR is 38, instead
> of 39
>>>
>>A known problem. You can tweak this in the toplevel CMakeLists.txt.
> Look for BO
21 matches
Mail list logo
