On Thu, Aug 07, 2008 at 04:03:32PM -0700, Michael Rogers wrote:
>Sorry Yaakov. I didn't mean to be annoying. You've been very helpful.
>
>I'll work on it tonight and send you more info tonight or tomorrow when
>I have it available. Basically all I meant by "not viable" was that
>the executibles
I haven't already figured the
problem out myself.
-Mike
--- On Thu, 8/7/08, Yaakov (Cygwin Ports) <[EMAIL PROTECTED]> wrote:
> From: Yaakov (Cygwin Ports) <[EMAIL PROTECTED]>
> Subject: Re: Can you make a DLL from a library that requires caller-defined
> functions?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Once again, http://cygwin.com/acronyms/#PCYMTWLL !
Michael Rogers wrote:
| The problem now that the linker doesn't like the undefined references
| for a static library any better then it does for a DLL. I can get
| a static library file if I just
les directly to the executible. That seems like the simplest solution
and I don't see why it won't work as long as I specify the X11 library
dependencies correctly at link time.
Mike
- Original Message
From: Yaakov (Cygwin Ports) <[EMAIL PROTECTED]>
To: cygwin-xfree@c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://cygwin.com/acronyms/#PCYMTWLL !
Michael Rogers wrote:
| Yes, precisely. It has symbols for routines that are declared in a
| header file and called in some of the library routines. But they
| are actually required to be defined in the call
I previously used the subject line "External functions in a (to a) DLL" but I
think this is more accurate.
Yaakov wrote:
-
If I follow you, you want to create a library that has undefined symbols
wh
