This is the mail archive of the gsl-discuss@sources.redhat.com mailing list for the GSL project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BORLAND C++


Hi Brian,

In the Borland C++ compiler is the some as far as I know.

When you build the dll you must define this variables as
__declspec(dllexport)

and when you write an application that use the dll you must define
the variable in you include files as
__declspec(dllimport)

I suppose that to solve that definitively , the source of the library should
be
modified so that the dll knows about these variable to be exported
using the __declspec(dllexport)  and when we use it in the program
using the __declspec(dllimport), at least to do it fully compatible with
Borland compiler (and perhaps MSCV??).


Regard



----- Original Message -----
From: "Brian Gough" <bjg@network-theory.co.uk>
To: "Santiago Calderon" <sacate@jazzfutboleros.com>
Cc: <gsl-discuss@sources.redhat.com>
Sent: Thursday, December 13, 2001 11:34 PM
Subject: Re: BORLAND C++
> The errors are related to static data (e.g. pointers) not being
> imported.  There is some information on the gnuwin32 site at
> http://gnuwin32.sourceforge.net/compile.html
>
> In MSVC the extension __declspec(dllimport) can be added to the header
> files to handle that, I don't know what other compilers do though.
>
> regards
> Brian
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]