Fresh buildsystem fails while server doesn't
Ralf Habacker
ralf.habacker at freenet.de
Tue Oct 27 21:23:55 CET 2009
Patrick Spendrin schrieb:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Casper van Donderen schrieb:
>
>> I deleted my KDE trunk yesterday to start all anew against Qt 4.6 but
>> it fails already at strigi.
>>
>
>
>> c:\KDE4>C:\KDE4\bin\jom.exe
>> jom 0.6.8 - empower your cores
>>
>> File Makefile doesn't exist.
>>
>> c:\KDE4>
>>
>>
>> That CMakeTmpQmake folder does not even exist.
>>
>> Then if I run jom/nmake from the build folder it just starts till it
>> encounters the following error:
>>
>> [ 77] Generating moc_filebrowser.cxx
>> 'QMAKESPEC" has not been set, so configuration cannot be "deduced.' is
>> not recognized as an internal or external command,
>> operable program or batch file.
>> command failed with exit code 1
>> command failed with exit code 2
>> [ 77] QProcess: Destroyed while process is still running.
>> command failed with exit code 2
>> command failed with exit code 2
>> command failed with exit code 2
>>
>>
>>
>> Any ideas why this is happening?
>>
> Please check if your Qt provides the mkspecs folder (look into
> %KDEROOT%\build\libs\qt-*\image*\mkspecs\win32-msvc2008). Somehow our Qt
> build fails from time to time to copy that one....
>
I recognized some fails when there is no mkspecs/default folder which
should be copied from the recent compiler mkspecs. I added some code to
the qt install step to create this by default.
Regards
Ralf
More information about the Kde-windows
mailing list