Stephan Kulow schrieb:
> Am Donnerstag, 9. November 2006 11:12 schrieb Stephan Kulow:
>> Am Donnerstag, 9. November 2006 10:50 schrieb Manuel Klimek:
>>> Hi,
>>>
>>> I'm just curious:
>>> was it already discussed to name the debug libraries *d.dll on windows?
>>> I don't want to start a 'religious'
Am Donnerstag, 9. November 2006 11:12 schrieb Stephan Kulow:
> Am Donnerstag, 9. November 2006 10:50 schrieb Manuel Klimek:
> > Hi,
> >
> > I'm just curious:
> > was it already discussed to name the debug libraries *d.dll on windows?
> > I don't want to start a 'religious' discussion ;-), but this
On Thu, 9 Nov 2006, Manuel Klimek wrote:
> I'm just curious:
> was it already discussed to name the debug libraries *d.dll on windows?
> I don't want to start a 'religious' discussion ;-),
You started it now! :P
> but this would allow release and debug builds side by side on windows,
> where de
Am Donnerstag, 9. November 2006 10:50 schrieb Manuel Klimek:
> Hi,
>
> I'm just curious:
> was it already discussed to name the debug libraries *d.dll on windows?
> I don't want to start a 'religious' discussion ;-), but this would
> allow release and debug builds side by side on windows, where deb
Hi,
I'm just curious:
was it already discussed to name the debug libraries *d.dll on windows?
I don't want to start a 'religious' discussion ;-), but this would
allow release and debug builds side by side on windows, where debug and
release libraries mustn't be mixed.
Greetings,
Manuel
Stephan Kulow schrieb:
> Hi!
>
> I found out why kpat requires QtCore4 - it links both against Core and
> Cored, everything in kdegames does: E.g.
>
> kdegames_LIB_DEPENDS:STATIC=C:/kde/qt-win-opensource-src-4.2.1/lib/QtCore4.lib;C:/kde/qt-win-opensource-src-4.2.1/lib/QtCored4.lib;kdecore;c:/kde
On Thu, 9 Nov 2006, Stephan Kulow wrote:
>> This is not necessarily about binary incompatibility but likely about a
>> heap conflict between the debug and release libraries. Opening kpat in
>> depends.exe is likely to show both msvcrt.dll and msvcrtd.dll in the list
>> of dependencies.
>
> Ah, tha
Am Donnerstag, 9. November 2006 09:00 schrieb Harri Porten:
> Sidenote:
>
> On Thu, 9 Nov 2006, Stephan Kulow wrote:
> > As you can see it links all Qt libs twice. If I remove the QtCore4.lib
> > manually, kpat starts up fine, if not it crashes in random places, which
> > indicate that kpat uses di
Sidenote:
On Thu, 9 Nov 2006, Stephan Kulow wrote:
> As you can see it links all Qt libs twice. If I remove the QtCore4.lib
> manually, kpat starts up fine, if not it crashes in random places, which
> indicate that kpat uses different (binary incompatible) QMap code than
> kdelibs does.
This is
Hi!
I found out why kpat requires QtCore4 - it links both against Core and
Cored, everything in kdegames does: E.g.
kdegames_LIB_DEPENDS:STATIC=C:/kde/qt-win-opensource-src-4.2.1/lib/QtCore4.lib;C:/kde/qt-win-opensource-src-4.2.1/lib/QtCored4.lib;kdecore;c:/kde/inst/lib/kdewin32d.lib;user32;shel
10 matches
Mail list logo