Re: [aspell-devel] Another Win32 build method

[Kevin Atkinson]

On Mon, 25 Nov 2002, Ruurd Reitsma wrote:

> 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 same way it is required for VC++?

> 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?

That attached patch should fix the problem.

-- 
http://kevin.atkinson.dhs.org

intel.diff
Description: Text document