On Sep 18, 2009 13:14 "Tuomo Latto" <djv@...> wrote:
> Bjørn Madsen wrote:
> > Because I get a load of "undefined reference" errors when doing the
> > final linking of .o files to a .dll.
> > I read through that link and tried every possible combination of
> > arguments I could come up with, and nothing changes. All errors are
> > for functions supplied in the library. One other thing, which might
> > have relevance, this is C++, and the library supplies a class which
> > exposes the needed functions (so I can't include it as extern C). I
> > am not that clear on the details, but are there some problems with
> > different compilers and function name mangling in C++? I think that
> > was what lead me on to the reimp path.
> Great, a single 500-character line of text...
> Short answer is you can't and shouldn't mix compilers with C++.
> AFAIK the problem is basically that the internal mechanisms and
> conventions used by different compilers to implement
> the language are, well, different and they don't mix.
> If you want to see that changed, at the bare minimum
> you need to get Microsoft to document the internals
> and then fully commit to that, have them place that
> documentation under some permissive enough public license
> and then wrestle with the GCC crowd (and other compiler
> makers) to get them to support that.
> To do that you don't need luck, you need divine powers.
> Just so you know this is a FAQ!
> Considering there is quite enough written documentation
> available, I am left wondering how come people don't read it.
Right. Thanks for the help.
Lose a bit of the hostility and this might have been a pleasant experience.