> -----Original Message----- > From: development-bounces+janne.anttila=digia....@qt-project.org > [mailto:development-bounces+janne.anttila=digia....@qt-project.org] On > Behalf Of Oswald Buddenhagen > Sent: 17. huhtikuuta 2012 12:44 > To: development@qt-project.org > Subject: Re: [Development] Moving checksdk.exe to qtbase repo > > On Tue, Apr 17, 2012 at 11:15:17AM +0200, ext Andreas Holzammer wrote: > > Am 17.04.2012 10:32, schrieb Oswald Buddenhagen: > > > integrate it into qmake, so it is able to produce self-contained > > > makefiles which don't need messing with the environment. > > > > And where should the mapping between sdk and mkspec go to? Or does the > > mkspec has then the sdk name in it? > > > i don't know really, i haven't dealt with the wince specs much. > one option is to have one spec per target config, which seems to be the > case already (to some degree?). you only need to add some variable to > the specs which would allow the dispatcher code in qmake to choose the > right build config. this could also be used to preset the right config > in the vcproj solution files. I wasn't aware of qmake ability to produce self-contained makefiles, so I will investigate approach suggested by Ossi.
What comes to mappings between mkspecs and sdks in setcepaths.bat, I also don't like it and my idea was to replace it with something like this (from my Qt4 development branch): http://pastebin.com/DZCgJJbW. WinCE mkspecs already have CE_SDK which can be used to query environment related settings with the help of checksdk.exe. -- Janne _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
