Larry Hall kirjoitti:
At 05:42 AM 3/27/2005, you wrote:
Hi all!
I was wondering what I have to do to get purely native win32 app to build under
cygwin. I know that -mnocygwin directive drops out dependency to cygwin1.dll,
but how about other libraries?
How I can make a separate sandbox for my pur
Could someone point me to a description of the
details of how shared library functions are
resolved at runtime? I'm trying to debug a
situation where a variable is supposed to
be initialized with a pointer to a dll-imported
function. It appears to be incorrectly
initialized, but I'm not really sure
At 05:42 AM 3/27/2005, you wrote:
>Hi all!
>
>I was wondering what I have to do to get purely native win32 app to build
>under cygwin. I know that -mnocygwin directive drops out dependency to
>cygwin1.dll, but how about other libraries?
>
>How I can make a separate sandbox for my purposes that in
I have seen the discussions at
http://sourceware.org/ml/cygwin/2004-09/msg01101.html
referenced at
http://cygwin.com/ml/cygwin/2005-03/msg00048.html
regarding gcc 3.3.3's placement of const symbols into
rdata which then cannot be properly initialized.
This problem seems pretty fundamental. Can anyo
Hi all!
I was wondering what I have to do to get purely native win32 app to
build under cygwin. I know that -mnocygwin directive drops out
dependency to cygwin1.dll, but how about other libraries?
How I can make a separate sandbox for my purposes that in any case even
two versions of libs exist
5 matches
Mail list logo
