[Ctk-developers] getting things to work in windows

[Mark Roden]

Yes, it looks like not using the sdk was the right call.  I'll now go
ahead with the cmake stuff as well.

Thanks for the help!

Mark

On Tue, Jan 18, 2011 at 7:56 AM, Mark Roden <mmroden at gmail.com> wrote:
> Ah, so making sure not to use the SDK sounds like the primary failure
> then.  I'll check it out.
>
> Thanks,
> Mark
>
> On Tue, Jan 18, 2011 at 7:44 AM, Sascha Zelzer
> <s.zelzer at dkfz-heidelberg.de> wrote:
>> What is your development environment?
>>
>> If you are using Visual Studio 2008 and want to create 32 bit binaries,
>> there is no reason to compile Qt yourself. Use the pre-build binaries for
>> Nokia: http://qt.nokia.com/downloads/windows-cpp-vs2008 (*NOT* the SDK, this
>> one is MinGW based) and set the QT_QMAKE_EXECUTABLE variable in CMake to
>> e.g. C:\Qt\4.7.1\bin\qmake.exe.
>>
>> - Sascha
>>
>> On 01/18/2011 03:25 PM, Mark Roden wrote:
>>>
>>> Hi Sascha,
>>>
>>> Thanks for this, I'll look into it this morning.
>>>
>>> I want to build Qt because cmake fails to find qt on my system when I
>>> use the sdk downloaded from qt.  The thought was that building Qt
>>> would allow cmake to see what it needs to see to include Qt.
>>>
>>> Thanks,
>>> Mark
>>>
>>> On Tue, Jan 18, 2011 at 1:44 AM, Sascha Zelzer
>>> <s.zelzer at dkfz-heidelberg.de>  wrote:
>>>>
>>>> Hi,
>>>>
>>>> looking at your command line, I see that you invoke configure from a Qt
>>>> SDK
>>>> installation directory. This SDK is MinGW based. If you want to build Qt
>>>> yourself, get the raw sources
>>>>
>>>> (http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.7.1.zip),
>>>> unpack them in a folder (without spaces in the name) and configure from
>>>> inside there.
>>>>
>>>> Why do you want to build Qt yourself in the first place? This should only
>>>> be
>>>> necessary if you want 64bit binaries or a Visual Studio 2010 compiled Qt.
>>>>
>>>> Best,
>>>> Sascha
>>>>
>>>> On 01/18/2011 06:52 AM, Mark Roden wrote:
>>>>>
>>>>> Running in administrator mode (which should have the same effect as
>>>>> turning off the UAC) does not solve the problem, but produces a new
>>>>> bug:
>>>>>
>>>>>
>>>>> mt.exe : general error c101008d: Failed to write the updated manifest
>>>>> to the resource of file "..\..\..\bin\idc.exe". Access is denied.
>>>>>
>>>>> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft
>>>>> SDKs\Windows\v6.0A\bin\mt.exe"' : return code '0x1f'
>>>>> Stop.
>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual
>>>>> Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2'
>>>>> Stop.
>>>>> NMAKE : fatal error U1077: 'cd' : return code '0x2'
>>>>> Stop.
>>>>>
>>>>> with the command line:
>>>>> D:\Qt\2010.05\qt>configure -release -platform win32-msvc2008 -no-dsp
>>>>> -no-vcproj
>>>>>
>>>>> I find it very hard to believe that I have a completely broken Qt
>>>>> installation, or that I'm the only one with this problem, yet there it
>>>>> is.
>>>>>
>>>>> I'll try again from scratch, maybe that will solve the issue.
>>>>>
>>>>
>>
>>
>