Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Thu, 15 Feb 2001 01:32:11 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Cc:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Subject:	Exporting symbols from a .exe
Message-ID:	<20010215013211.A2451@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com,
	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i

I know that in a past life I was able to export symbols from a normal
executable without too much work.

If I do something like the following, however, 'foo' never shows up as an
exported symbol:

int __declspec(dllexport)
foo()
{
  return 1;
}

int
main(int argc, char **argv)
{
  puts ("hello world");
}

The above produces an executable file with an exported "foo" function
when linked with Visual C.  foo() never seems to be exported when linked
with the current binutils, though.

So, this is a bug, right?  I could really use this functionality for an
performance improvement idea that I have for Cygwin.

cgf

- Raw text -