delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/11/29/19:08:58

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
From: "Paul G." <pgarceau AT attbi DOT com>
Organization: Paul G.
To: cygwin AT cygwin DOT com
Date: Fri, 29 Nov 2002 16:09:03 -0800
MIME-Version: 1.0
Subject: .dll.a, .dll files and other questions
Reply-to: pgarceau AT attbi DOT com
Message-ID: <3DE7911F.32407.278E3D@localhost>

Hi folks,

	Just had a couple of questions.  Attempting to head off a problem at the pass...

	When using gcc -shared, what is default output (ie. what is expected from gcc -
shared in order to read the .dlls/shared files) by Cygwin?

	Second question:  If g++ -shared is used will the output .dll/shared files be loadable 
and/or useable by Win32 api?

	Finally, I realize that if g++ -shared, if used, is likely going to generate name 
mangled .dlls that can not be read/loaded properly by the win32api.

	Is that still true for Cygwin?

	Thanks,

		Paul G.

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

- Raw text -


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