Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <008f01c41ca5$fa19e880$033310ac@kwcorp.com>
From: "Jay West" <jwest AT classiccmp DOT org>
To: "Cygwin List" <cygwin AT cygwin DOT com>
Subject: Fw: Will using cygwin help with back-linking?
Date: Wed, 7 Apr 2004 08:41:06 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Forgot to copy to list...
----- Original Message ----- 
From: "Jay West" <jwest AT classiccmp DOT org>
To: "Jani tiainen" <redetin AT luukku DOT com>
Sent: Wednesday, April 07, 2004 8:40 AM
Subject: Re: Will using cygwin help with back-linking?


> You wrote...
> > You don't have to, I did it already.. =)
> Thanks so much for the advice!!
>
> > Basicaly thing goes so that you compile (but not link) needed files,
> > generate needed .lib:s and then link whole thing.
> Ok, that gives me an idea for how to proceed. From the reading I did on
> libtool, there's an excellent section on how to deal with this. I just
> didn't like the answer they gave there and was hoping cygwin provided "the
> magic". The libtool page I was reading said either only work on platforms
> that support backlinking, or, make the main executable a "stub exe &
> separate library" so that all objects wishing to be shared are stuffed in
a
> library. Then link that library with the modules. I really didn't want to
> have to totally reorganize the code but it sounds like what you are
advising
> is pretty much the same approach.
>
> In my specific case, each module ("plug-in") has subroutines with the same
> names. In the dlopen/dlsym world, this is ok as only one module is
dlopened
> at a time. Hopefully the "linking against libraries" method won't obviate
> this and complain about duplicate symbols.
>
> > <http://mail.gnu.org/archive/html/libtool/2002-10/msg00145.html>
> >
> > <http://sources.redhat.com/ml/cygwin/2003-12/msg01071.html>
> Awesome! Teach a man to fish.... :)
>
> > Because this is strictly windoze specific, this is also a offtopic of
> > this mailinglist..
> Yes, now that I see cygwin doesn't magically get around the backlinking
> issue, you're right - it becomes strictly a windows centric problem. I do
> wonder if something couldn't be added to cygwin like it's own module
loader
> that did take care of backlinking - if that's at all possible. As I
> understand it, it would sure make it easier to port unix code to windows
and
> that's what cygwin is all about :)
>
> Thanks so much... back to the coding table!
>
> Jay West
>

---
[This E-mail scanned for viruses by Declude Virus]


--
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/