Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <43511148.1030609@brasse.org> Date: Sat, 15 Oct 2005 16:25:12 +0200 From: =?UTF-8?B?TWF0dGlhcyBCcsOkbmRzdHLDtm0=?= User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: boost, boost_unit_test_framework References: <434AE423 DOT 6070701 AT brasse DOT org> <434B95C0 DOT 8030200 AT sh DOT cvut DOT cz> <434E0EC3 DOT 4040502 AT brasse DOT org> <434F8064 DOT 5080100 AT sh DOT cvut DOT cz> <434F83F6 DOT 4030607 AT brasse DOT org> <4350EA7F DOT 5050203 AT sh DOT cvut DOT cz> In-Reply-To: <4350EA7F.5050203@sh.cvut.cz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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/