www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2002/04/18/16:14:38

Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "Waldo Bastian" <bastian AT kde DOT org>, "Cygwin-Apps" <cygwin-apps AT cygwin DOT com>
Subject: FW: libtool devel package still dll crippled.
Date: Thu, 18 Apr 2002 22:14:20 +0200
Message-ID: <004601c1e715$a022f6e0$651c440a@BRAMSCHE>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal

Hi Waldo,

currently some guys are porting libtool to cygwin and have troubles with static
libs in multiple dll's and they like to hear how this is solved in linux.
Perhaps if you can't answer these question, please send it to somebody who can.

1. When someone build a shared lib on linux and uses a static lib, are the
symbols of the static lib automatically  exported ?

2a. If yes, and if someone build a second dll with the same static lib, the
symbols of the static libs are in both
shared lib defined. Then if someone uses these two shared libs to build for
example an application, ld fails with duplicated symbol errors. How does ld
prevent this ?

2b If no, that means that the static lib in 1. is used only for resolving
undefined symbols in the shared lib.
If someone likes to build some static sublibs like kicker does and builds a
shared dll with them, how does ld ensure, that the static libs symbols are
exported ?

Thanks for answering.

BTW: QT3 is just ported to cygwin.

Regards

Ralf

- Raw text -


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