Projects/KDE on Windows/Windows CE - Revision history

Neverendingo: Text replace - "" to ""

2011-06-29T20:57:32Z

Text replace - "</code>" to "</syntaxhighlight>"

Neverendingo: Text replace - "`" to ""`


2011-06-29T20:49:03Z
Text replace - "<code>" to "<syntaxhighlight lang="text">"

				
				
				
				
			
			← Older revision
			Revision as of 20:49, 29 June 2011
			
Line 37:
Line 37:
  The following program outputs the known folders:   The following program outputs the known folders:
    
− <code> + <syntaxhighlight lang="text">
  #include <windows.h>   #include <windows.h>
  main()   main()



Aheinecke: Update the introduction to better reflect the current state of kde wince and this page
2011-02-11T11:27:55Z
Update the introduction to better reflect the current state of kde wince and this page

				
				
				
				
			
			← Older revision
			Revision as of 11:27, 11 February 2011
			
Line 1:
Line 1:
  == Introduction ==   == Introduction ==
    
− This page describes a work in progress, there are no KDE Applications running on Windows Mobile (that I know of). It is only intended to give a starting point to developers for cross compilation and Windows CE related issues. Since Qt is already ported for Windows CE it should be possible to get some KDE applications running on that Platform.   + '''This page is mostly deprecated''' it was started for a Project to port Kdepim to Windows CE. All additional patches / cross compile techniques can be found in emerge from the KDE - Windows initative.
  + Binaries for Windows Mobile 6.5 and a source tarball of Kontact Touch (an optimized variant of KDEPIM software for Touch enabled devices) can be found at:
  + http://files.kolab.org/local/windows-ce/Kontact-Mobile/testing/latest/ 
    
  =====Windows CE / Windows Mobile=====   =====Windows CE / Windows Mobile=====



Marcus at 18:19, 30 July 2010
2010-07-30T18:19:34Z


				
				
				
				
			
			← Older revision
			Revision as of 18:19, 30 July 2010
			
Line 506:
Line 506:
  [http://msdn.microsoft.com/en-us/library/bb446118.aspx MSDN Messaging Reference]   [http://msdn.microsoft.com/en-us/library/bb446118.aspx MSDN Messaging Reference]
  [http://msdn.microsoft.com/en-us/library/aa914277.aspx MSDN POOM Reference]   [http://msdn.microsoft.com/en-us/library/aa914277.aspx MSDN POOM Reference]
  + 
  + === Debugging with emerge ===



Aheinecke: Fixed a link
2010-03-30T07:36:13Z
Fixed a link

				
				
				
				
			
			← Older revision
			Revision as of 07:36, 30 March 2010
			
Line 159:
Line 159:
  To install the console:   To install the console:
       Download and install (in Windows!) the        Download and install (in Windows!) the
− [http://www.microsoft.com/downloads/details.aspx?familyid=74473FD6-1DCC-47AA-AB28-6A2B006EDFE9&displaylang=en + [http://www.microsoft.com/downloads/details.aspx?familyid=74473FD6-1DCC-47AA-AB28-6A2B006EDFE9&displaylang=en Microsoft Windows Mobile Developer Power Toys]
− Microsoft Windows Mobile Developer Power Toys] + 
       Copy cmd.exe, console.dll, shell.exe in \windows on device        Copy cmd.exe, console.dll, shell.exe in \windows on device
       Set HKEY_LOCAL_MACHINE/Drivers/Console/OutputTo to 0          Set HKEY_LOCAL_MACHINE/Drivers/Console/OutputTo to 0  
Line 185:
Line 184:
  ==== Security Configuration Manager ====   ==== Security Configuration Manager ====
  To control the security configuration for your device there is a tool from   To control the security configuration for your device there is a tool from
− Microsoft: + Microsoft: [http://www.microsoft.com/downloads/details.aspx?FamilyID=7e92628c-d587-47e0-908b-09fee6ea517a&DisplayLang=en
− [http://www.microsoft.com/downloads/details.aspx?FamilyID=7e92628c-d587-47e0-908b-09fee6ea517a&DisplayLang=en + 
  Device Security Manager PowerToy for Windows Mobile 5.0]     Device Security Manager PowerToy for Windows Mobile 5.0]  
    



Marc: /* Building Qt */ markup; mention checksdk.exe not found solution; use the mkspec for the HTC Touch Pro 2
2010-03-26T16:04:34Z
‎Building Qt:  markup; mention checksdk.exe not found solution; use the mkspec for the HTC Touch Pro 2

				
				
				
				
			
			← Older revision
			Revision as of 16:04, 26 March 2010
			
Line 210:
Line 210:
  <br>   <br>
    
− ==== Building Qt<br>  ==== + ==== Building Qt ====
    
− Download the Qt libraries for Windows CE from http://qt.nokia.com/downloads/win-ce-cpp and extract it, you may want to make sure that your path contains no blanks to avoid some problems.<br>Now you should add your &lt;qt-directory&gt;\bin to your Windows PATH environment variable (which can be done from “''Control Panel → System → Advanced →Environment variables''” ) + Download the Qt libraries for Windows CE from http://qt.nokia.com/downloads/win-ce-cpp and extract it, you may want to make sure that your path contains no blanks to avoid some problems.
    
− Next get up your Visual Studio Command Prompt which should be accessible from the Windows Start Menu. Change the working directory to qt-directory and start the configuration. There should be a configuration.exe in your qt-directory with the usual options, (configure.exe -help for more info) for cross compiling you need to give at least the -platform parameter with your host system and -xplatform with your cross-compile target. Supported platforms are listed in the README file. e.g.: + Now you should add your <tt>&lt;qt-directory&gt;\bin</tt> to your Windows <tt>PATH</tt> environment variable (which can be done from “''Control Panel → System → Advanced →Environment variables''”, user and system <tt>PATH</tt>s are merged by Windows).
    
− configure.exe -platform win32-msvc2008 -xplatform wincewm60standard-msvc2008 + Next get up your Visual Studio Command Prompt which should be accessible from the Windows Start Menu. Change the working directory to qt-directory and start the configuration. There should be a <tt>configure.exe</tt> in your qt-directory with the usual options, (<tt>configure.exe -help</tt> for more info) for cross compiling you need to give at least the <tt>-platform</tt> parameter with your host system and <tt>-xplatform</tt> with your cross-compile target. Supported platforms are listed in the <tt>README</tt> file. e.g.: 
    
− Now that your configuration is set you can start the cross compilation. To switch from your “normal” build environment to the wince target Qt has a nice script included in the /bin directory (which should be in your PATH) just try calling setcepaths and provide your target configuration.<br>setcepaths wincewm60standard-msvc2008<br>With nmake (Visual Studio version of make) you can now build Qt for your target system. +   configure.exe -platform win32-msvc2008 -xplatform wincewm65professional-msvc2008  
    
− <br>   + Now that your configuration is set you can start the cross compilation. To switch from your “normal” build environment to the wince target Qt has a nice script included in the <tt>/bin</tt> directory (which should be in your <tt>PATH</tt>): just try calling <tt>setcepaths</tt> and provide your target configuration.
  +   setcepaths wincewm65professional-msvc2008
  + (if this complains that it cannot find <tt>checksdk.exe</tt>, you are building out-of-source (shadow builds in Qt lingo) and you need to add <tt>&lt;builddir&gt;\bin</tt> to <tt>PATH</tt>, too, then re-run the script).
  + With <tt>nmake</tt> (Visual Studio version of make) you can now build Qt for your target system.
    
  == Building Qt for Windows CE with CeGCC  ==   == Building Qt for Windows CE with CeGCC  ==



Marcus: more info
2010-03-26T02:59:01Z
more info

				
				
				
				
			
			← Older revision
			Revision as of 02:59, 26 March 2010
			
Line 76:
Line 76:
  CreateProcess must get both first arguments, name and cmdline.  In contrast to Windows NT (and Unix), cmdline must not repeat the name of the executable as argv[0].  Instead, argv[0] is filled in from the module name, and cmdline fills the arguments starting from argv[1].   CreateProcess must get both first arguments, name and cmdline.  In contrast to Windows NT (and Unix), cmdline must not repeat the name of the executable as argv[0].  Instead, argv[0] is filled in from the module name, and cmdline fills the arguments starting from argv[1].
    
  + The only handles that can be duplicated to other processes are Mutexes, Semaphores and Events. These can also simply be opened by their name from different processes for a similar effect.  No way to pass File or other handles from one process to another!  Must use socketpair (named object by port) or custom device driver (named object by device).
  + 
  + ExitProcess is missing.  ExitThread from main thread terminates the whole process!
    
  == Device Setup for Windows Mobile for Development ==   == Device Setup for Windows Mobile for Development ==



Marc: /* Setting up Visual Studio */ typo
2010-03-25T14:54:47Z
‎Setting up Visual Studio:  typo

				
				
				
				
			
			← Older revision
			Revision as of 14:54, 25 March 2010
			
Line 201:
Line 201:
  ==== Setting up Visual Studio<br>  ====   ==== Setting up Visual Studio<br>  ====
    
− First thing you need is Visual Studio professional or standard edition (preferably with service pack 1). Be aware that the express editions are explicitly not supported for Windows CE development.<br> (You could use [http://www.microsoft.com/downloads/details.aspx?FamilyId=1DACDB3D-50D1-41B2-A107-FA75AE960856&displaylang=en%20 Microsoft Embedded VC] which is cost-free, but depreciated and not supported by Qt) <br>Next thing you need is a Microsoft Windows Mobile Platform SDK corresponding to your target platform. Just search the Microsoft download pages or get the Windows Mobile 6 SDK from [http://www.microsoft.com/downloads/details.aspx?FamilyID=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en here] (You should take a loot at the System Requirements)<br>If everything is set up correctly you should now be able to create a “Visual C++ smart device" project in Visual Studio.<br>   + First thing you need is Visual Studio professional or standard edition (preferably with service pack 1). Be aware that the express editions are explicitly not supported for Windows CE development.<br> (You could use [http://www.microsoft.com/downloads/details.aspx?FamilyId=1DACDB3D-50D1-41B2-A107-FA75AE960856&displaylang=en%20 Microsoft Embedded VC] which is cost-free, but deprecated and not supported by Qt) <br>Next thing you need is a Microsoft Windows Mobile Platform SDK corresponding to your target platform. Just search the Microsoft download pages or get the Windows Mobile 6 SDK from [http://www.microsoft.com/downloads/details.aspx?FamilyID=06111A3A-A651-4745-88EF-3D48091A390B&displaylang=en here] (You should take a loot at the System Requirements)<br>If everything is set up correctly you should now be able to create a “Visual C++ smart device" project in Visual Studio.<br>  
  Note on Version-Naming: Standard means without touchscreen, Professional means with Touchscreen and Classic means Windows Mobile without mobile phone capabilities<br>     Note on Version-Naming: Standard means without touchscreen, Professional means with Touchscreen and Classic means Windows Mobile without mobile phone capabilities<br>  
    
  More about Visual Studio and Windows Mobile development: http://msdn.microsoft.com/en-us/library/dd721907.aspx   More about Visual Studio and Windows Mobile development: http://msdn.microsoft.com/en-us/library/dd721907.aspx
− <br>   + <br>
    
  ==== Building Qt<br>  ====   ==== Building Qt<br>  ====



Aheinecke: Reworked the tools part
2010-03-19T15:29:50Z
Reworked the tools part
Show changes


Marcus at 10:39, 16 March 2010
2010-03-16T10:39:09Z


				
				
				
				
			
			← Older revision
			Revision as of 10:39, 16 March 2010
			
Line 71:
Line 71:
  39 - [\My Documents\Eigene Bilder]   39 - [\My Documents\Eigene Bilder]
  </pre>   </pre>
  + 
  + === Further differences ===
  + 
  + CreateProcess must get both first arguments, name and cmdline.  In contrast to Windows NT (and Unix), cmdline must not repeat the name of the executable as argv[0].  Instead, argv[0] is filled in from the module name, and cmdline fills the arguments starting from argv[1].
    
  == Useful Windows Mobile Tools ==   == Useful Windows Mobile Tools ==

@@ Line 52: / Line 52: @@
+   }
+}
-</code>
+</syntaxhighlight>
 Output:

← Older revision		Revision as of 18:19, 30 July 2010
Line 506:		Line 506:
	[http://msdn.microsoft.com/en-us/library/bb446118.aspx MSDN Messaging Reference]		[http://msdn.microsoft.com/en-us/library/bb446118.aspx MSDN Messaging Reference]
	[http://msdn.microsoft.com/en-us/library/aa914277.aspx MSDN POOM Reference]		[http://msdn.microsoft.com/en-us/library/aa914277.aspx MSDN POOM Reference]
		+
		+	=== Debugging with emerge ===

← Older revision		Revision as of 02:59, 26 March 2010
Line 76:		Line 76:
	CreateProcess must get both first arguments, name and cmdline. In contrast to Windows NT (and Unix), cmdline must not repeat the name of the executable as argv[0]. Instead, argv[0] is filled in from the module name, and cmdline fills the arguments starting from argv[1].		CreateProcess must get both first arguments, name and cmdline. In contrast to Windows NT (and Unix), cmdline must not repeat the name of the executable as argv[0]. Instead, argv[0] is filled in from the module name, and cmdline fills the arguments starting from argv[1].

		+	The only handles that can be duplicated to other processes are Mutexes, Semaphores and Events. These can also simply be opened by their name from different processes for a similar effect. No way to pass File or other handles from one process to another! Must use socketpair (named object by port) or custom device driver (named object by device).
		+
		+	ExitProcess is missing. ExitThread from main thread terminates the whole process!

	== Device Setup for Windows Mobile for Development ==		== Device Setup for Windows Mobile for Development ==