Václav Haisman wrote:
<@boost!libs!test!build>libboost_prg_exec_monitor.dll
This is exactly the same error I get.
This is strange. When I get the test libraries to build I used a bjam
binary that I downloaded from source forge:
http://peterhost.dl.sourceforge.net/sourceforge/boost/boost-j
Mattias Brändström wrote:
> Václav Haisman wrote:
>
>> Well, it definitely doesn't work for me. I don't think I have in any way
>> non-standard Cygwin installation.
>>
>> It would be helpful if you could download the -src package of Boost
>> using setup.exe, extract it and run the build-boost.sh
Václav Haisman wrote:
Well, it definitely doesn't work for me. I don't think I have in any way
non-standard Cygwin installation.
It would be helpful if you could download the -src package of Boost
using setup.exe, extract it and run the build-boost.sh script. Don't
forget to remove the --without
Well, it definitely doesn't work for me. I don't think I have in any way
non-standard Cygwin installation.
It would be helpful if you could download the -src package of Boost
using setup.exe, extract it and run the build-boost.sh script. Don't
forget to remove the --without-test line or make it in
Václav Haisman wrote:
Mattias Brändström wrote:
bjam -sTOOLS=gcc --with-test stage
And that command produced the test libraries for me. The only difference
from your libraries was that their extension was .lib instead of .a. How
did you manage to get .a libraries? Is there any difference betwee
Mattias Brändström wrote:
> Václav Haisman wrote:
>
>>>
>>> Have the test libraries worked in any previous version of boost for
>>> Cygwin? If so, is there any way that I can install that version instead?
>>
>>
>> I don't know. The current Boost package is the only Boost Cygwin package
>> so far.
Václav Haisman wrote:
Have the test libraries worked in any previous version of boost for
Cygwin? If so, is there any way that I can install that version instead?
I don't know. The current Boost package is the only Boost Cygwin package
so far. You could try to compile some older Boost than 1.3
Mattias Brändström wrote:
> Václav Haisman wrote:
>
>>>
>>> /usr/lib/libboost_date_time-gcc-mt-s-1_33.a*
>>> /usr/lib/libboost_date_time-gcc-mt-s.a*
>>
>>
>> This is called 'versioned' layout.
>>
>>
>>> In my build scripts I would still like to be able to specify
>>> -lboost_date_time and not -lbo
Václav Haisman wrote:
/usr/lib/libboost_date_time-gcc-mt-s-1_33.a*
/usr/lib/libboost_date_time-gcc-mt-s.a*
This is called 'versioned' layout.
In my build scripts I would still like to be able to specify
-lboost_date_time and not -lboost_date_time-gcc-mt-s. Is it the
intention of the maintai
Mattias Brändström wrote:
> Hello!
>
> I want to write some C++ programs that use boost and compile them using
> cygwin. What is the recomended way of doing this?
>
> Usually when I use the boost libraries (on Fedora Core) I would be able
> to link my program using gcc by providing -lboost_date
Hello!
I want to write some C++ programs that use boost and compile them using
cygwin. What is the recomended way of doing this?
Usually when I use the boost libraries (on Fedora Core) I would be able
to link my program using gcc by providing -lboost_date_time on the
command line. With cygwi
11 matches
Mail list logo
