[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-buildsystem
Subject:    mingw status
From:       syntheticpp () gmx ! net (=?ISO-8859-1?Q?Peter_K=FCmmel?=)
Date:       2006-02-20 13:41:13
Message-ID: 43F9C6F9.8050302 () gmx ! net
[Download RAW message or body]

Thiago Macieira wrote:
> Peter K?mmel wrote:
>> The only solution I see, is to move the UString code from
>> /khtml/ecma/kjs_binding.cpp into a extra file (kjs_ustring.cpp?) and to
>> build this file with kjs, not with khtml.
>>
>> But this we have to discuss with the khtml people.
> 
> You don't have to. This will never happen.
> 
We don't have to change any kjs code.

> KJS can't link to Qt.
> 
Even not in our cmake files?
It's a KDE only solution.

> By design, this one function must be declared in another library.
> 
I don't understand.
Currently it's declared in kjs and defined in khtml.

The problem when compiling khtml is that some files of khtml
include ustring.h and get the info UString::UString(const QString&)
is somewhere in a dll, but this constructor is implemented in by khtml
itself, so you get linker errors.

A other solution could be to move the khtml-ustring implementation into a
mini-dll.

Maybe I've overlooked the simples solution: Could I declare a single member
function with a other linkage as the rest of the class?

Peter

[prev in list] [next in list] [prev in thread] [next in thread]