--- Heiko Gerdau <hg@...> wrote:
> Could you create a small example that shows the problem so that we
> can check
> with our setups. We don't see any linking problems with the standard
> using a cross compiler here.
I'm afraid not. We have a huge codebase and the problem occurs
somewhere in the middle of it. I would be unable to test that snippet
out with our standard build scripts without making massive changes to
The problem is with very simple statements such as:
Everywhere else foo is referenced, similar errors pop up. As you can
see, the headers have been included, which bears out the fact that the
problem is at link time.
Could someone just outline any particular steps and compiler switches
they use while building a dll? Is there a guide somewhere? I've looked
through the existing documentation numerous times but have found no
clearcut steps that work. Also, if someone could tell me which compiler
switches are absolutely needed to generate a working Windows executable
(I know mms-bitfields is), that would be a big help.
> As far as I remember your cross compiler is pre build. Maybe
> rebuilding it
> from source might solve the problem.
True, it is. My initial attempts were to rebuild it, but I was having
several problems doing that with several different scripts I tried. I
haven't tried your directly, but one that was derived from yours did
not work. The time constraints led to the choice of a prebuilt
The prebuilt one seems to work ok. I tried simple Qt apps that used
stringstreams and strings, and was able to generate EXEs without a
problem. Since the same compiler and libraries were used, this suggests
that the problem may be with my build environment and the way the
libraries are found. Maybe it's trying to use native libraries. I'm
looking into this.
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.