Automotive Cluster Display Demo for WinCE6

I see there is a nice Automotive Cluster Display Demo on the Developer Center (here) but it is for Qt 4.8.4 with WinCE7.
I’d like to try it on VF61 module with WinCE6, but when I load into VS2008 I see the error message
"The project consists entirely of configurations that require support for platforms which are not

installed on this machine. The project can not be loaded"

Since I’m a beginner with Toradex module I don’t know if I should modify something either in VS2008 or in the project itself to have it working under WinCE6.

I downloaded the executable with the required DLL and it runs under Win CE6, but I can’t compile a working example from the supplied source code.

Hey,

Thank you for trying that demo. Here some steps how I was able to get the example compiled from source:

  1. Download http://developer.toradex.com/files/toradex-dev/uploads/media/Colibri/WinCE/Special/QT/qt-win-opensource-4.8.4-vs2008_Toradex_WinCE6_NO_GL.exe

  2. Install it to standard path, otherwise its not working correct

  3. Download and install Toradex Documents - Toradex CE6 SDK

  4. Apply patch http://docs.toradex.com/102861-patch-qt-win-opensource-4-8-4-vs2008-toradex-wince6-no-gl.zip to Qt

  5. Maybe apply http://docs.toradex.com/102482-updatesdknames.zip as well, to your Qt installation

  6. Download Automotive sources from here: www.kdab.com/~andy/QtAutomotiveClusterDemo.zip

  7. create a build folder somewhere next to the deflated sources.

  8. open VS command line

  9. Navigate to created build folder

  10. type in C:\Qt\4.8.4\bin\qmake.exe <path to sources>

  11. Open in Visual Studio 2008 the project file which got created

  12. Open project settings and change under debugging and deployment all occurrences from %CSIDL_PROGRAM_FILES% to \flashdisk

  13. make sure conmanclient2 and cmaccept are started on target(beware you need to connect to target in 2 minutes after starting cmaccept, otherwise you need to run it again)

  14. Tools → Options… → Device Tools → Devices → Select Toradex_CE600 → Properties → Configure … → Use specific IP address and fill in your targets ip address. Click 2 x ok

  15. Start debugging and see after a while the application on the screen of the Colibri VF61

Hint: Conmanclient2 was crashing when I tried to deploy the application a second time, files on flashdisk needed to be deleted before deploying again.

Hi,
I followed your instructions step-by-step, but at step #10 I get the following output from qmake

Usage: C:\Qt\4.8.4\bin\qmake.exe [mode] [options] [files]

QMake has two modes, one mode for generating project files based on
some heuristics, and the other for generating makefiles. Normally you
shouldn't need to specify a mode, as makefile generation is the default
mode for qmake, but you may use this to test qmake on an existing project

Mode:
  -project       Put qmake into project file generation mode
                 In this mode qmake interprets files as files to
                 be built,
                 defaults to *.c; *.ui; *.y; *.l; *.ts; *.xlf; *.qrc; *.h; *.hpp; *.hh; *.hxx; *.cpp; *.cc; *.cxx
                 Note: The created .pro file probably will 
                 need to be edited. For example add the QT variable to 
                 specify what modules are required.
  -makefile      Put qmake into makefile generation mode (default)
                 In this mode qmake interprets files as project files to
                 be processed, if skipped qmake will try to find a project
                 file in your current working directory

Warnings Options:
  -Wnone         Turn off all warnings; specific ones may be re-enabled by
                 later -W options
  -Wall          Turn on all warnings
  -Wparser       Turn on parser warnings
  -Wlogic        Turn on logic warnings (on by default)
  -Wdeprecated   Turn on deprecation warnings (on by default)

Options:
   * You can place any variable assignment in options and it will be     *
   * processed as if it was in [files]. These assignments will be parsed *
   * before [files].                                                     *
  -o file        Write output to file
  -d             Increase debug level
  -t templ       Overrides TEMPLATE as templ
  -tp prefix     Overrides TEMPLATE so that prefix is prefixed into the value
  -help          This help
  -v             Version information
  -after         All variable assignments after this will be
                 parsed after [files]
  -norecursive   Don't do a recursive search
  -recursive     Do a recursive search
  -set <prop> <value> Set persistent property
  -unset <prop>  Unset persistent property
  -query <prop>  Query persistent property. Show all if <prop> is empty.
  -cache file    Use file as cache           [makefile mode only]
  -spec spec     Use spec as QMAKESPEC       [makefile mode only]
  -nocache       Don't use a cache file      [makefile mode only]
  -nodepend      Don't generate dependencies [makefile mode only]
  -nomoc         Don't generate moc targets  [makefile mode only]
  -nopwd         Don't look for files in pwd [project mode only]

Do you have an idea on the reason?

Ups my bad

  1. type in C:\Qt\4.8.4\bin\qmake.exe <path to sources>

Sorry for the inconvenience. But this page was choking my <> part

Sorry for the late answer. Most likely you are using a space in your path, which might need wrapping into quotes or even better dont use paths with spaces.

Thank you

Andy

This is not a problem Andy.
As a matter of fact you had already answered to my message on qmake error with your comment below your original answer.
You had already edited the original answer with the right step #10 command

C:\Qt\4.8.4\bin\qmake.exe <path to sources>