problem configurating qt for vs2008

mrjj

@Hamed
SP 1 at least.
https://www.microsoft.com/en-us/download/details.aspx?id=10986

Hamed

@mrjj said in problem configurating qt for vs2008:

oh, also , it seems to be a commercial options.
So it must mean you have a license.
So you can get dedicated direct help if you contact them. \o/

It's commercial option? really? I have opensource one.
The docs doesn't say this is for commercial version only!

mrjj

@Hamed
no, sorry. it just seems like that. It seems optional :)

Hamed

@mrjj said in problem configurating qt for vs2008:

@Hamed
SP 1 at least.
https://www.microsoft.com/en-us/download/details.aspx?id=10986

I checked and yes, SP1 installed.

mrjj

@Hamed
then i guess 5.6 is better to use.
I assume that 5.8 uses type_traits and vs 2008 didnt have back then.

Hamed

@mrjj said in problem configurating qt for vs2008:

@Hamed
then i guess 5.6 is better to use.
I assume that 5.8 uses type_traits and vs 2008 didnt have back then.

OK I will download Qt5.6.
If that didn't work I will use Qt4.8.
If none of them work I will continue posting state here.
Thank you for your time and help.

mrjj

@Hamed
np. i did read the docs a bit more careful and it seems that 5.6 is the version for wince and
it must be 2008 as wince died in later versions.

And yes by all means do come back if it wont compile.
There might be other users that use wince still.
Such a cute little windows :)

Hamed

And another thing I remembered to say, I already installed and have qt5.7 on my device.
Could this be the source of problem? Should I delete this one or I can have them both?

mrjj

@Hamed
You can have as many as u want.
Just make sure u use the correct one.
Normally its not an issue or source of problem but im old school so if you dont need it. delete it :)

Hamed

@mrjj I'm need it but not more than this one, for the last solution I will do that.
Thank you again.

Hamed

@mrjj I downloaded Qt5.6 source (low speed internet) and the README file is different and it meets my requirements (C++ compiler supporting the C++98 standard) , but the strange part is I'm getting the following output :

+ cd qtbase
+ C:\Qt2\Qt5.6.0\qtbase\configure.bat -top-level -platform -xplatform wincewm70customsdk-msvc2008
Unknown option wincewm70customsdk-msvc2008
Invalid option "-xplatform" for -platform.
See the README file for a list of supported operating systems and compilers.
Invalid option "wincewm70customsdk-msvc2008" for -xplatform.

Any Idea?

mrjj

@Hamed said in problem configurating qt for vs2008:

incewm70customsdk-msvc2008

no, ill ask for assistance and hope :)

Hamed

@mrjj Thank you

SGaist

Hi,

Following Installing Qt for Windows CE which refers to the Qt for Windows CE Requirements which itself refers to the Windows CE - Working with Custom SDKs page, there's an explanation about how to setup a toolchain to match your needs.

Hope it helps

Hamed

@SGaist said in problem configurating qt for vs2008:

Hi,

Following Installing Qt for Windows CE which refers to the Qt for Windows CE Requirements which itself refers to the Windows CE - Working with Custom SDKs page, there's an explanation about how to setup a toolchain to match your needs.

Hope it helps

Uh I didn't check that docs carefully in first place.
I think this would be the solution, I will test it as soon as I got home.
Thank you.

mrjj

@Hamed
Yeah me me neither. Missed that part. alt text
Ill cross fingers.

Hamed

Thanks to @SGaist and @mrjj problem solved.
I post some information in case someone faced this problem later :
1- Qt docs says run this command :

configure -platform -xplatform [wince_custom_build_specification_directory_name]

This will not work, instead run :

configure -xplatform [wince_custom_build_specification_directory_name]

2- This specification directories are in Qt\Qt[Version]\qtbase\mkspecs
3- Find your destination platform directory there or simply create one.
4- open qmak.conf file in that directory and set CE_SDK to your SDK name (mine was STANDARDSDK_500) and set CE_ARCH to your destination device architecture for example ARMV4I

Hope this helps.

After all these steps my configuration works fine but when I run nmake I get following errors :

C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\altcecrt.h(363) : error C2733: second C linkage of overloaded function 'wcsftime' not allowed
        C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\altcecrt.h(363) : see declaration of 'wcsftime'
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\altcecrt.h(391) : error C3861: 'memcpy_s': identifier not found
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\altcecrt.h(396) : error C3861: 'memmove_s': identifier not found
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\iosfwd(584) : error C2039: 'memcpy_s' : is not a member of '`global namespace''
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\iosfwd(584) : error C3861: 'memcpy_s': identifier not found
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\iosfwd(608) : error C2039: 'memmove_s' : is not a member of '`global namespace''
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\ce\include\iosfwd(608) : error C3861: 'memmove_s': identifier not found
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\\ce\bin\x86_arm\cl.EXE"' : return code '0x2'
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.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'cd' : return code '0x2'
Stop.

Should I start new thread for this problem or not?

Hamed

Any idea about this issue?
I think this problem is not related to Qt, but if anyone could help me solve these errors would be great.

mrjj

@Hamed
It seems related to wince/mobile and i can find many mention those errors
but saw no solution.
https://forum.qt.io/topic/62184/cross-compile-qt-5-5-on-wince-6-0-6-5-windows-embedded-handheld-6-5-classic/2

Hamed

@mrjj yeap, this is exactly the problem and as you said no solution...