public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Serguei DACHIAN <Serguei.Dachian@univ-lemans.fr>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Making DLL's
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <199903212347.RAA09201@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990331194500.TDsQezboaYs2EH0KHgMXOTrW-Loqh41tABxaszAZ5TE@z> (raw)
In-Reply-To: <1.5.4.32.19990321230358.00671530@lola.univ-lemans.fr>

Serguei DACHIAN <Serguei.Dachian@univ-lemans.fr> writes:
> Thanks to everybody who answered.  Now I see that my script is indeed
> useless since "dllwrap" does all the nessecary job.  But why in the User's
> guide and in the FAQ there is not a word about dllwrap!!!???  


No doc because nobody's bothered to write it; I haven't had the
motivation/time. Contribution in texinfo format will be more than 
appreciated of course. The README file in my dllhelpers package
does document most of it, and the rest are scattered throughout the 
various examples I've published so far, eg., howto make java jni.

> The  only thng
> that is talled about DLL making is that old complicated method that I used
> in the script.  The place where I was able to find an excelent documentation
> about DLL making was not the CygWin cite, but
> >
> > http://www.xraylith.wisc.edu/~khan/software/gnu-win32/dllhelpers.html
> >
> I think User's guide and/or FAQ must at least point there.

Yes, this is a good idea. 

dllwrap is nothing but a hack, but I needed it and it does the job. Here's
to hoping that we can soon put this hack to rest, thanks to DJ who has
rewritten the PE linker. There are still a few quirks in it, but that'll 
all get flushed out/fixed after a bit of use.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-21 15:04 Serguei DACHIAN
     [not found] ` < 1.5.4.32.19990321230358.00671530@lola.univ-lemans.fr >
1999-03-21 15:47   ` Mumit Khan [this message]
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Serguei DACHIAN
  -- strict thread matches above, loose matches on Subject: below --
1999-03-18 13:07 Serguei DACHIAN
1999-03-19  3:30 ` Paul Sokolovsky
1999-03-19  6:01   ` Sebastien Carpe
     [not found]     ` < 36F258AB.CC1A1788@atos-group.com >
1999-03-19  7:30       ` DJ Delorie
1999-03-22  2:32         ` Gary V. Vaughan
1999-03-22  7:28           ` John Mullee
1999-03-22  8:56             ` Gary V. Vaughan
1999-03-31 19:45               ` Gary V. Vaughan
1999-03-31 19:45             ` John Mullee
     [not found]           ` < u1zihvmrf.fsf@oranda.demon.co.uk >
1999-03-22 14:50             ` Fergus Henderson
1999-03-23  1:47               ` Gary V. Vaughan
1999-03-31 19:45                 ` Gary V. Vaughan
1999-03-31 19:45               ` Fergus Henderson
1999-03-31 19:45           ` Gary V. Vaughan
1999-03-31 19:45         ` DJ Delorie
1999-03-31 19:45     ` Sebastien Carpe
1999-03-31 19:45   ` Paul Sokolovsky
1999-03-31 19:45 ` Serguei DACHIAN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199903212347.RAA09201@modi.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=Serguei.Dachian@univ-lemans.fr \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).