Re: I think too many problem, nothing work properly

defresco wrote: > I send the cmake-log but some text is in italian language I hope it's good > for search the problem, thanks all. Thanks, seems it could not find user32lib. Have you installed the Platform SDK? To use the IDE you most tell it that there is a platform SDK: Open Visual C++, go to T

RE: I think too many problem, nothing work properly

I send the cmake-log but some text is in italian language I hope it's good for search the problem, thanks all. From: defresco [mailto:[EMAIL PROTECTED] Sent: Thursday, November 09, 2006 4:26 PMTo: kde-buildsystem@kde.orgSubject: I think too many problem, nothing work properly   I'm using

Re: I think too many problem, nothing work properly

defresco wrote: > > I'm using "Microsoft Visual c++ Express edition" on compiling Dbus, when > type command "cmake -G"Visual Studio 8 2005" I see too many error that i not > understand. Cmake don't work with ide on my PC. If I use Nmake it compile > only the debug version. I'm really frustrated.

I think too many problem, nothing work properly

  I'm using "Microsoft Visual c++ Express edition" on compiling Dbus, when type command "cmake -G"Visual Studio 8 2005" I see too many error that i not understand. Cmake don't work with ide on my PC. If I use Nmake it compile only the debug version. I'm really frustrated. Someone can tell me

Re: QtCore4.dll

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'

Re: QtCore4.dll

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

Re: QtCore4.dll

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

Re: QtCore4.dll

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

Re: QtCore4.dll

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

Re: QtCore4.dll

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

Re: QtCore4.dll

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

Re: QtCore4.dll

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