hi
there!
i'm currently
working on wgcc v2 and the libltdl behaviour on windows. looking at
mdemo-static.test and co. i have a little problem. since all libs are linked in
static, the symbols which are looked up are contained in the executeable itself,
so my idea was to dlopen the execute
Hello Markus,
* Duft Markus wrote on Thu, Sep 07, 2006 at 03:45:01PM CEST:
>
> i'm currently working on wgcc v2 and the libltdl behaviour on windows.
> looking at mdemo-static.test and co. i have a little problem. since all
> libs are linked in static, the symbols which are looked up are contain
Danny Smith wrote:
> Thinking more about this, the whole problem goes away with
> -funit-at-a-time and that is turned on by default at
> optimization level of 1 or higher.
Not the whole problem, only the case of a reference in the same compilation
unit as the definition of the variable.
> It see
> I would consider such a tool usable only
> if it had no arbitrary limits, such as a maximum size of 65000 bytes for
> an exports list
I have to eat my words: the exports list is _not_ limited in size by wgcc.
Sorry.
Bruno
___
http://
>
> I propose to make 'dllexport' unnecessary, and to make it
> possible to use 'dllimport' everywhere where the users were
> used to write either 'dllimport' or 'dllexport', depending on
> the compilation pass and unit.
I think what bothers me most is that this will encourage people to use
Hello Bruno,
* Bruno Haible wrote on Wed, Sep 06, 2006 at 07:00:31PM CEST:
>
> > Slightly related question: are you planning on providing a means to
> > automatically rename gnulib functions to a library-specific namespace?
> > As long as there is no policy on interface stability for gnulib, I wo
* Bruno Haible wrote on Wed, Sep 06, 2006 at 06:37:08PM CEST:
> Danny Smith wrote:
>
> > There is dangerous ambiguity. In the past this kind of ambiguity
> > cause most of the dllimport-related ICE's in GCC.
>
> I assume that GCC has enough maintainers to fix ICEs inside GCC.
But it's not Libto
