[aspell-devel] Another Win32 build method

[Ruurd Reitsma]

Hi,

judging from the mailing list, building on win32 is quite popular, so here's
another approach. (AFAIK a mingw .dll cannot be debugged when used with a MSVC
app, and the MSVC port seems a bit crude)

When using Visual Studio 6 with Intel C++ 6.0 & STLport, the aspell .dll
(vanilla 0.50.2) compiles with a few small hickups. That is, when combining
commom with the aspell lib into one .dll, and adding the proper dllexport
nonsense to the C frontend.

The only error I'm getting is:

D:\Dev\aspell-0.50.2\common\config.cpp(433): error: more than one user-defined
conversion from "acommon::PosibErr<acommon::String>" to "acommon::String"
applies:
            function "acommon::String::String(acommon::ParmString)"
            function "acommon::String::String(const acommon::String &)"
       String s1 = retrieve(replace);

This can be circumvented by commenting out:

    String(ParmString s) : std::string(s) {}

in the String class, and changing this back and forth during compilation. The
result is a .dll that is binary compatible with VC++.

Any hints on fixing this one error?

Cheers,

Ruurd

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus – Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com