-------------------------------------------------------------------------------- From: Swartz Ed (Nokia-D/Austin) Sent: Wednesday, December 16, 2009 9:21 AM To: Paul Warren (Nokia-D/Austin); Podwall Dan (Nokia-D/Austin); Kelly Tim (Nokia-D/Austin) Cc: King Ronnie (Nokia-D/Austin) Subject: RE: [S60 Qt Developers] RE: Can't import pro file to Carbide in MCL10.1 sdk > I don't think Carbide is responsible for making sure the Qt variables are setup correctly are we? It sounds like we at least need feedback on this from the Qt tools team. [[[ejs]]] Yes, I agree, we're not responsible for them. Another issue I see is that the builder appears to use only global settings for invoking Qmake, but as we see here, different SDKs may have different builds of qmake and different ideas about how to invoke it and set up its variables. We can't ask the user to restart Carbide and change their global QMAKESPEC to build a Qt project under a different SDK. > So it's not a simple question of which plugin calls qmake.*? If it's the Qt Eclipse plugin, we can log the bug and they can decide if calling qmake.bat is the right fix or not. We don't call qmake.{exe,bat} directly in any case. But we do ask the Qt makefile builder (in the Qt Eclipse plugin) to run qmake for us, in two places. (All I was saying is, that can afford us some control to fix this issue in the short term, but it won't fix the issue in all cases where the builder is run on its own.) Sounds like we need to ask whether the Qt makefile builder makes use of any per-project (or better, per-CDT-configuration) properties which we can set to override the global Qt preferences. (BTW, I don't think qmake.bat is appropriate if it's a Symbian-specific thing. The builder is generic and qmake.bat doesn't exist in the Qt SDK.) > Is that a yes or no? Yes :) -- Ed -------------------------------------------------------------------------------- From: Swartz Ed (Nokia-D/Austin) Sent: Wednesday, December 16, 2009 8:52 AM To: Podwall Dan (Nokia-D/Austin); Paul Warren (Nokia-D/Austin); Kelly Tim (Nokia-D/Austin) Cc: King Ronnie (Nokia-D/Austin) Subject: RE: [S60 Qt Developers] RE: Can't import pro file to Carbide in MCL10.1 sdk We call the QMakeRunner from the QtProFileImportWizard and ProjectCreatedTasksQt process, but it accepts environment variable overrides, so we could probably fix this there... But I think the Qt Makefile builder itself will get called during normal builds if the user edits the *.pro file, so fixing the two places above wouldn't be a full solution. -- Ed -------------------------------------------------------------------------------- From: Podwall Dan (Nokia-D/Austin) Sent: Wednesday, December 16, 2009 8:42 AM To: Paul Warren (Nokia-D/Austin); Kelly Tim (Nokia-D/Austin) Cc: King Ronnie (Nokia-D/Austin); Swartz Ed (Nokia-D/Austin) Subject: Fwd: [S60 Qt Developers] RE: Can't import pro file to Carbide in MCL10.1 sdk I expect that it's the Qt Eclipse plugin calling qmake, not Carbide? If that's correct let me know and I'll log a bug in the Qt bug tracker. Begin forwarded message: From: "Mantila Janne (Nokia-D/Tampere)" Date: December 16, 2009 6:21:39 AM CST To: "Riskedal Espen (Nokia-D-Qt/Oslo)" , "Alamaki Tero (Nokia-D/Oulu)" Cc: "Huttunen Sampo (Nokia-D/Oulu)" , "Swartz Ed (Nokia-D/Austin)" , "Kelly Tim (Nokia-D/Austin)" , "s60qt@lists.research.nokia.com" Subject: RE: [S60 Qt Developers] RE: Can't import pro file to Carbide in MCL10.1 sdk In 10.1 MCL release QMAKESPEC is set by \epoc32\tools\qmake.bat I would guess carbide is using qmake.exe from \epoc32\tools\qt\qmake.exe So either define QMAKESPEC by yourself or fix the carbide to use qmake.bat -Janne -----Original Message----- From: s60qt-bounces@lists.research.nokia.com [mailto:s60qt-bounces@lists.research.nokia.com] On Behalf Of Riskedal Espen (Nokia-D-Qt/Oslo) Sent: 16.12.2009 12:47 To: Alamaki Tero (Nokia-D/Oulu) Cc: Kelly Tim (Nokia-D/Austin); Huttunen Sampo (Nokia-D/Oulu); Swartz Ed (Nokia-D/Austin); s60qt@lists.research.nokia.com Subject: Re: [S60 Qt Developers] RE: Can't import pro file to Carbide in MCL10.1 sdk Alamaki Tero (Nokia-D/Oulu) skrev: Defining QMAKESPEC helped to mee too! I now start carbide with the following kind of bat script and importing my pro file succeeds: Defining QMAKESPEC is fine, but it shouldn't be necessary really, typically the default QMAKESPEC is stored in .qmake.cache inside the Qt directory. My guess it's not being picked up correctly by qmake (sombody copied it somwere wrong) and therefore qmake defaults back to another QMAKESPEC (typically win32-something). I'd guess whoever broke up / moved qmake should fix this :) espen