public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cwilson@ece.gatech.edu>
To: tmii@mbnet.fi
Cc: cygwin@cygwin.com
Subject: Re: "Best" way to build a DLL?
Date: Sun, 10 Feb 2002 18:34:00 -0000	[thread overview]
Message-ID: <3C672DDA.2080902@ece.gatech.edu> (raw)
In-Reply-To: <21W5184CAEB3VLIS65OJ64IC74WUNK.3c658c3a@middlevalue>

Take a look at the new examples in the dllhelpers.  I've added four new 
examples for building DLLs using libtool and friends.

--Chuck

Nousiainen wrote:

 > This seems to be the most complicated thing .. building a DLL file. So,
 >  what is the best and recommended way to do the job using recent
 > cygwin tools?
 >
 > I've read autobook
 > (http://sources.redhat.com/autobook/autobook/autobook_toc.html) and
 >  it gives some good advice (I'm using autotools in my project),
 > though there are some problems  I've encountered. It recommends
 > using _LTLIBRARIES and libtool to build DLL, and as far as I know
 > the building process of a DLL file is already integrated in gcc and
 >  ld, so is the document  outdated? (I have to use both C and C++
 > code in my project, and when specifying AC_PROG_CXX in configure.in
 >  file the configure script doesn't succeed, because it tries to
 > execute a file  called ltconfig which doesn't exist. I really don't
 >  have a clue what to do here...) Dllhelpers
 > (http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/index.html)
 >  show another, simple way (using the new dll features of ld) to
 > build the file and it is the only way I have  managed to build a
 > working DLL. However, I don't have an idea how to get this working
 > smoothly with autotools.
 >
 > So, what should I do? I'd appreciate if someone gave me an example
 > of the configuration files for autotools (Makefile.am and
 > configure.in).


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2002-02-11  2:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09 12:55 Nousiainen
2002-02-09 21:20 ` undefined reference to `<libname>_dll_a_iname' using dllwrap Andrej Falout
2002-02-10 18:34 ` Charles Wilson [this message]
2002-02-11  8:24 "Best" way to build a DLL? Gerald S. Williams
2002-02-11 10:44 ` Gerald S. Williams
2002-02-11 10:53   ` Charles Wilson
2002-02-11 10:51 ` Charles Wilson
2002-02-15 12:27   ` Jason Tishler
2002-02-15 12:52     ` Gerald S. Williams
2002-02-15 13:06       ` Jason Tishler

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=3C672DDA.2080902@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=tmii@mbnet.fi \
    /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).