Bernard Dautrevaux wrote:
> > -Original Message-
> > From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
> > Subject: Re: DLL naming conventions
> >
>
>
>
> This scheme seems to work for me also; the only think I would like to have,
> when
Exported data needs to be treated specially by the application; the
compiler must construct the program to access the data indirectly.
This is different from functions, which can be indirected through the
import library. The linker cannot adjust the program to fix such
data references if the com
On Mon, Sep 04, 2000 at 09:34:12PM +0300, Paul Sokolovsky wrote:
>Mandatory data imports marking: I *hate* this feature and develop
>libtool re-implementation which frees programmer from it. But when I
>mentioned it on cygwin maillist, DJ Delorie was rather sceptical about
>it, saying they will su
On Sun, Sep 03, 2000 at 04:39:51PM -0300, Alexandre Oliva wrote:
> On Sep 3, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>
> > * When installing a libtool (.la) library:
> > - libfoo.la goes to $prefix/lib
> > - libfoo.dll goes to $prefix/bin
> > - libfoo.dll.a goes to
> -Original Message-
> From: Gary V. Vaughan [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 03, 2000 2:05 PM
> To: Charles Wilson
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: DLL naming conventions
>
> > It doesn't work for M
On Sep 3, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
> * When installing a libtool (.la) library:
> - libfoo.la goes to $prefix/lib
> - libfoo.dll goes to $prefix/bin
> - libfoo.dll.a goes to $prefix/lib
> - libfoo.a goes to $prefix/lib
Nope. libfoo.la g
On Sun, Sep 03, 2000 at 01:34:23AM -0400, Charles Wilson wrote:
> "Gary V. Vaughan" wrote:
>
> > > Now, suppose that the png folks release a newer version, say png-2.1.x
> > > that exposes some additional features, but is backwards compatible with
> > > png-2.0.x. Great. You build it, but creat
"Gary V. Vaughan" wrote:
> >
> > Also, there are two separate issues being discussed here: (1) how to
> > (compile-time) link against the 'right' version of a library, and (2)
> > how to insure that the 'right' dll is loaded at run-time.
>
> Nah. I'm talking about (2) only. I *am* assuming that
On Sat, Sep 02, 2000 at 02:36:03PM -0400, Charles S. Wilson wrote:
> "Gary V. Vaughan" wrote:
> >
> > Charles S. Wilson wrote:
> > >
> > > There is *something* in the windows system that gets notified that
> > > myapp.exe depends on mydll.dll whenever you execute myapp.exe. This
> > > *something
"Gary V. Vaughan" wrote:
>
> Charles S. Wilson wrote:
> >
> > There is *something* in the windows system that gets notified that
> > myapp.exe depends on mydll.dll whenever you execute myapp.exe. This
> > *something* searches the file system according to the search path
> > described earlier in
10 matches
Mail list logo
