This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: boost, boost_unit_test_framework


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 between .a
and .lib in Cygwin?

Are you sure that you are using Cygwin's GCC? Or even any GCC? For me, Boost produces only .a archives or .dlls.


Yes, I am quite sure. I use a freshly installed Cygwin and I guess that the boost build scripts will compile with gcc if I compile the way I descibed above.


In what way is the test libraries broken under Cygwin?

Unless I add --without-test I get this error after which the whole build process tops:

unknown target type for
<@boost!libs!test!build>libboost_prg_exec_monitor.dll


Have you tried to just compile the test libraries? If I remember correctly, building dynamic test libraries is indeed broken under Cygwin but static libraries should work.


:.:: mattias

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]