delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/01/27/08:11:13

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: <40165F54.7010502@luukku.com>
Date: Tue, 27 Jan 2004 14:53:40 +0200
From: Jani Tiainen <redetin AT luukku DOT com>
User-Agent: Mozilla Thunderbird 0.5a (Windows/20040120)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problem with DLLs and processes
References: <OFE433A7FD DOT 578BD292-ON80256E28 DOT 00452205 AT db DOT com>
In-Reply-To: <OFE433A7FD.578BD292-ON80256E28.00452205@db.com>
X-IsSubscribed: yes

Przemyslaw Sliwa wrote:

> Woooooww,
> 
> It seems it is much more complicated than just the simple STATIC option in GCC under Linux.
> But there must be a way to link the executable with the dlls. Like in Linux.

There really isn't way. There is some ways to get around it, like 
bundling that DLL inside application, and load it from there.

Doesn't Linux need also static libs if you're are compiling statically 
linked? Or is Linux able to link dynamic libraries as static..? (Don't 
remember been so long time I fuzzed around with Linux compilation).

Other funny caveats are unbounded, or external symbols inside dynamic 
library. In linux they're solved at run time, in DLL you really have to 
solve them at link time... =)


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


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