Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Thu, 20 Oct 2005 18:31:54 -0400 (EDT)
From:	Jason Pyeron <jpyeron AT pdinc DOT us>
To:	cygwin AT cygwin DOT com
Subject:	Re: making .so files...
In-Reply-To:	<43581990.2090108@users.sourceforge.net>
Message-ID:	<Pine.LNX.4.62.0510201831170.8995@ns.pyerotechnics.com>
References:	<Pine DOT LNX DOT 4 DOT 62 DOT 0510171807380 DOT 5147 AT ns DOT pyerotechnics DOT com> <43581990 DOT 2090108 AT users DOT sourceforge DOT net>
MIME-Version:	1.0
X-IsSubscribed:	yes

On Thu, 20 Oct 2005, Yaakov S (Cygwin Ports) wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jason Pyeron wrote:
>> I am working with the Asterisk application, it uses "modules" these are
>> .so files which are linked against the main executable.
>>
>> Asterisk will load a module, which may or may not make use of code
>> exported by the main executable.
>
> If I understand you correctly, then it's not so difficult; I've done it
> myself with bmp, gedit, gthumb, liferea, and xmms.
>
> I don't know Asterisk, but it doesn't appear to use autotools; this
> makes things more difficult, especially if you want to make a portable
> patch.
>
> First, make sure that the asterisk executable is built *first*; you may
> need to precede '.' to the SUBDIRS variable (i.e. SUBDIRS = . subdir1
> subdir2 etc.)
>
> Add the following to the asterisk executable's LDFLAGS:
> '-Wl,--export-all-symbols,--out-implib,libasterisk.dll.a'
>
> Then, add the following to all the modules LDFLAGS, specifying the
> correct location: '-Wl,/path/to/libasterisk.dll.a'.
>
> Of course, make sure that all requisite link libraries are specified in
> LIBS for both the executable and the modules.
>
> You'll still need to find some way of making all this dependent on
> Cygwin in the Makefiles in order to make this portable.
>
>

I will try it this weekend, this is good to know.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                      PD Inc. http://www.pdinc.us -
- Partner & Sr. Manager             7 West 24th Street #100     -
- +1 (443) 921-0381                 Baltimore, Maryland 21218   -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information. If you 
have received it in error, purge the message from your system and 
notify the sender immediately.  Any other use of the email by you 
is prohibited.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -