On Thu, Nov 10, 2005 at 10:25:40AM -0800, Brian Dessent wrote:
> Thomas Porschberg wrote:
>
> > because libcppunit was built as cygwin-library. I resolved the
> > problem by compiling the library from sources with -mno-cygwin
> > flag. And then I used this library for both, my application
> > cygw
Thomas Porschberg wrote:
> because libcppunit was built as cygwin-library. I resolved the
> problem by compiling the library from sources with -mno-cygwin
> flag. And then I used this library for both, my application
> cygwin-build and my application mingw-build.
> If I understand you right, this
Hi Brian,
thanks for your explanation. I'm quite new to cygwin/mingw
and so my questions are probably very basic.
The idea on my side is to have sources which can be compiled
as an cygwin application or as a mingw/windows application.
The working environment is cygwin. The distinction between
wind
Thomas Porschberg wrote:
> This is of course nice but can someone give an explanation ?
What do you want an explantion of? The fact that you can't mix and
match Cygwin and non-Cygwin objects in an executable? That's because
mingw and Cygwin use different C runtimes. It boils down to the fact
t
Hi,
I have a problem when using the boost::program::options library
under cygwin in conjunction with building a application which
I compile with the "-mno-cygwin -mwindows" options.
I get a "undefined reference error to _environ" at link time.
I guess the problem arised because boost libraries (ve
5 matches
Mail list logo
