delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1998/03/01/08:20:07

From: mlx AT san DOT rr DOT com (Steve Biskis)
Subject: Hip, Hip, Hooray for b19
1 Mar 1998 08:20:07 -0800 :
Message-ID: <199803011559.HAA29481.cygnus.gnu-win32@proxyb2.san.rr.com>
Reply-To: <mlx AT san DOT rr DOT com>
Mime-Version: 1.0
To: <gnu-win32 AT cygnus DOT com>

All I've got to say is WAY TO GO guys,

Especially for your work on the cygwinb19.dll init internals !!!

Special thanks to Ton Van Overbeek for the sneaky
"spawn-thread/init-cygwin/fake-main-callback/hang-it-in-limbo" hack.
It definitely did NOT work w/b18 and delphi-3 executables.
EXTRA special thanks to whoever reworked those dll init internals.

Its nice to finally be able to use dlls compiled w/gnu-win32 as, well,
dlls.
But shouldn't cygwinbXX.dll initialize its per-process internals upon
process 
attachment regardless of whether or not it finds a main or WinMain ?

Maybe this new version already can do this and I just missed it.


1 more question:

Whats the difference between libgcc.a & libc.a?
It looks like libc is the one used by the dll since you get 
"_impure_ptr redefined" warnings if you try to put it and -lcygwin 
on a link line together but things still compile.  So what are the
pros and cons of linking one vs. the other ?

da bisk


 







-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019