summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorJoerg Bornemann <joerg.bornemann@nokia.com>2009-09-02 11:28:58 (GMT)
committerJoerg Bornemann <joerg.bornemann@nokia.com>2009-09-02 11:30:11 (GMT)
commit9539327f5f94ee41272ffdec3fe9edf7e9ac9642 (patch)
treede165223fad20822d73ffd0f387fb57951c92390 /doc
parentbd16db2c8b402c1faa2b03bb249f8aa7a44a8602 (diff)
downloadQt-9539327f5f94ee41272ffdec3fe9edf7e9ac9642.zip
Qt-9539327f5f94ee41272ffdec3fe9edf7e9ac9642.tar.gz
Qt-9539327f5f94ee41272ffdec3fe9edf7e9ac9642.tar.bz2
Doc: Windows CE introduction updated to mention VS 2008
Reviewed-by: mauricek
Diffstat (limited to 'doc')
-rw-r--r--doc/src/installation.qdoc2
-rw-r--r--doc/src/wince-introduction.qdoc23
2 files changed, 14 insertions, 11 deletions
diff --git a/doc/src/installation.qdoc b/doc/src/installation.qdoc
index 031c6da..e4007d3 100644
--- a/doc/src/installation.qdoc
+++ b/doc/src/installation.qdoc
@@ -661,7 +661,7 @@ in the \l{Qt for Windows CE Requirements} document.
\brief Setting up the Windows CE environment for Qt.
\previouspage General Qt Requirements
- Qt is known to work with Visual Studio 2005 and the following SDKs for
+ Qt is known to work with Visual Studio 2005/2008 and the following SDKs for
Windows CE development on Windows XP and Windows Vista:
\list
diff --git a/doc/src/wince-introduction.qdoc b/doc/src/wince-introduction.qdoc
index c867848..3fb8d37 100644
--- a/doc/src/wince-introduction.qdoc
+++ b/doc/src/wince-introduction.qdoc
@@ -52,8 +52,11 @@
\section1 Required tools
In order to use Qt for Windows CE you need to have Visual Studio
- 2005 and at least one of the supported Windows CE/Mobile SDKs
- installed.
+ 2005 or 2008 and at least one of the supported Windows
+ CE/Mobile SDKs installed.
+ Note, that the Visual Studio 2008 Standard Edition doesn't come
+ with Windows CE support. You will need the Professional Edition,
+ if you're using Visual Studio 2008.
We recommend the \e{Windows Mobile 5.0 SDK for Pocket PC} SDK available
\l{http://www.microsoft.com/downloads/details.aspx?FamilyID=83a52af2-f524-4ec5-9155-717cbe5d25ed&amp;DisplayLang=en}{here}.
@@ -71,15 +74,15 @@
Once you have a \c .pro file, there are two ways of building your
application. You can either do it on the command line or inside of
- VS2005. To do it on the command line, simply write:
+ Visual Studio. To do it on the command line, simply write:
\snippet doc/src/snippets/code/doc_src_wince-introduction.qdoc 0
- To build the project inside of VS2005, on the command line write:
+ To build the project inside of Visual Studio, on the command line write:
\snippet doc/src/snippets/code/doc_src_wince-introduction.qdoc 1
- then start VS2005 with the generated \c .vcproj or \c .sln file and
+ then start Visual Studio with the generated \c .vcproj or \c .sln file and
select \e{Build project}.
For more information on how to use qmake have a look at the \l
@@ -89,20 +92,20 @@
In order to run the application, it needs to be deployed on the
Windows CE/Mobile device you want to test it for. This can either
- be done manually or automated using VS2005.
+ be done manually or automated using Visual Studio.
To do it manually, simply copy the executable, the Qt \c{.dll}
files needed for the application to run, and the C-runtime library
into a folder on the device, and then click on the executable to
start the program. You can either use the \e Explorer found in
- ActiveSync or the \e{Remote File Viewer} found in VS2005 to do
+ ActiveSync or the \e{Remote File Viewer} found in Visual Studio to do
this.
- VS2005 can do this step automatically for you as well. If you have
- built the project inside VS2005, simply select \e Deploy and then
+ Visual Studio can do this step automatically for you as well. If you have
+ built the project inside Visual Studio, simply select \e Deploy and then
\e Debug to deploy and then run the application. You can change the
device type by changing the \e{Target Device} specified in the
- VS2005 toolbar.
+ Visual Studio toolbar.
Further information on deploying Qt applications for Windows can
be found in the \l{Deploying an Application on Windows}