Changeset 846 for trunk/doc/src/getting-started
- Timestamp:
- May 5, 2011, 5:36:53 AM (14 years ago)
- Location:
- trunk
- Files:
-
- 7 edited
- 3 copied
Legend:
- Unmodified
- Added
- Removed
-
trunk
- Property svn:mergeinfo changed
/branches/vendor/nokia/qt/4.7.2 (added) merged: 845 /branches/vendor/nokia/qt/current merged: 844 /branches/vendor/nokia/qt/4.6.3 removed
- Property svn:mergeinfo changed
-
trunk/doc/src/getting-started/demos.qdoc
r651 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 47 33 \previouspage Qt Examples 48 34 \contentspage How to Learn Qt 49 \nextpage What's New in Qt 4. 635 \nextpage What's New in Qt 4.7 50 36 51 37 This is the list of demonstrations in Qt's \c demos directory. … … 54 40 Qt. 55 41 56 \table 50%42 \table 57 43 \header 58 44 \o {2,1} Getting an Overview 59 45 \row 60 46 \o \inlineimage qtdemo-small.png 61 \o 62 If you run the \l{Examples and Demos Launcher}, you'll see many of Qt's 47 \o If you run the \l{Examples and Demos Launcher}, you'll see many of Qt's 63 48 widgets in action. 64 49 … … 128 113 129 114 \list 130 \o \l{demos/chip}{40000 Chips} uses the 131 \l{The Graphics View Framework}{Graphics View} framework to efficiently 132 display a large number of individual graphical items on a scrolling canvas, 133 highlighting features such as rotation, zooming, level of detail control, 134 and item selection. 135 \o \l{demos/embeddeddialogs}{Embedded Dialogs} showcases Qt 4.4's \e{Widgets on 136 the Canvas} feature by embedding a multitude of fully-working dialogs into a 137 scene. 115 \o \l{demos/chip}{40000 Chips} uses the \l{Graphics View Framework} to 116 efficiently display a large number of individual graphical items on 117 a scrolling canvas and highlighting features including rotation, 118 zooming, level of detail control, and item selection. 119 \o \l{demos/embeddeddialogs}{Embedded Dialogs} showcases Qt 4.4's 120 \e{Widgets on the Canvas} feature by embedding several 121 fully-functional dialogs in a scene. 138 122 \o \l{demos/boxes}{Boxes} showcases Qt's OpenGL support and the 139 integration with the Graphics View framework.123 integration with the \l{Graphics View Framework}. 140 124 \endlist 141 125 … … 151 135 152 136 \list 153 \o \l{Web Browser} demonstrates how Qt's \l{QtWebKit Module}{WebKit module} 154 can be used to implement a small Web browser. 137 \o \l{Web Browser} demonstrates how Qt's \l{QtWebKit} module can be used to 138 implement a small Web browser. 139 \endlist 140 141 \section1 Multimedia 142 143 \list 144 \o \l{demos/spectrum}{Spectrum Analyser} shows how the \l{QtMultimedia} 145 module can be used to manipulate audio as it is played. 155 146 \endlist 156 147 … … 158 149 159 150 \list 160 \o \l{demos/qmediaplayer}{Media Player} demonstrates how the \l{Phonon Module} can be 161 used to implement a basic media player application. 151 \o \l{demos/qmediaplayer}{Media Player} demonstrates how the 152 \l{Phonon Module}{Phonon module} can be used to implement a basic media player 153 application. 162 154 \endlist 163 155 164 156 \note The Phonon demos are currently not available for the MinGW platform. 157 158 \section1 Multimedia 159 160 \list 161 \o \l{demos/spectrum}{Spectrum Analyzer} demonstrates how the \l{QtMultimedia Module} 162 can be used to capture and play back an audio stream, at the same time allowing the 163 application to access the raw audio data. This application analyzes the audio stream 164 in order to display a frequency spectrum. 165 \endlist 165 166 166 167 \section1 Animation … … 187 188 \o \l{demos/embedded/lightmaps}{Light Maps} demonstrates OpenStreetMap integration with WebKit. 188 189 \o \l{demos/embedded/raycasting}{Ray Casting} demonstrates the use of ray casting with the 189 \l{ The Graphics View Framework}{Graphics View} framework.190 \l{Graphics View Framework}. 190 191 \o \l{demos/embedded/styledemo}{Embedded Styles} demonstrates the use of styles. 191 192 \o \l{demos/embedded/weatherinfo}{Weather Info} fetches weather information from the Web. -
trunk/doc/src/getting-started/examples.qdoc
r769 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 41 27 42 28 /*! 43 \page examples-overview.html 44 \raw HTML 45 <script> 46 document.location.href = "examples.html"; 47 </script> 48 \endraw 49 Click this \l{Qt Examples}{link} if you don't get redirected. 50 */ 51 52 /*! 53 \page examples.html 54 \title Qt Examples 55 \brief The example programs provided with Qt. 56 57 \previouspage Tutorials 58 \contentspage How to Learn Qt 59 \nextpage Qt Demonstrations 60 61 Qt is supplied with a variety of examples that cover almost every aspect 62 of development. They are not all designed to be impressive when you run 63 them, but their source code is carefully written to show good Qt 64 programming practices. You can launch any of these programs from the 65 \l{Examples and Demos Launcher} application. 66 67 These examples are ordered by functional area, but many examples often 68 use features from many parts of Qt to highlight one area in particular. 69 If you are new to Qt, you should probably start by going through the 70 \l{Tutorials} before you have a look at the 71 \l{mainwindows/application}{Application} example. 72 73 In addition to the examples and the tutorial, Qt includes a 74 \l{Qt Demonstrations}{selection of demos} that deliberately show off 75 Qt's features. You might want to look at these as well. 76 77 \section1 \l{Widgets Examples}{Widgets} 78 \beginfloatleft 79 \l{Widgets Examples}{\inlineimage widget-examples.png 80 } 81 82 \endfloat 83 Qt comes with a large range of standard widgets that users of modern 84 applications have come to expect. You can also develop your own custom 85 widgets and controls, and use them alongside standard widgets. 86 87 It is even possible to provide custom styles and themes for widgets that can 88 be used to change the appearance of standard widgets and appropriately 89 written custom widgets. 90 91 \clearfloat 92 \section1 \l{Dialog Examples}{Dialogs} 93 \beginfloatleft 94 \l{Dialog Examples}{\inlineimage dialog-examples.png 95 } 96 97 \endfloat 98 Qt includes standard dialogs for many common operations, such as file 99 selection, printing, and color selection. 100 101 Custom dialogs can also be created for specialized modal or modeless 102 interactions with users. 103 104 \clearfloat 105 \section1 \l{Main Window Examples}{Main Windows} 106 \beginfloatleft 107 \l{Main Window Examples}{\inlineimage mainwindow-examples.png 108 } 109 110 \endfloat 111 All the standard features of application main windows are provided by Qt. 112 113 Main windows can have pull down menus, tool bars, and dock windows. These 114 separate forms of user input are unified in an integrated action system that 115 also supports keyboard shortcuts and accelerator keys in menu items. 116 117 \clearfloat 118 \section1 \l{Layout Examples}{Layouts} 119 \beginfloatleft 120 \l{Layout Examples}{\inlineimage layout-examples.png 121 } 122 123 \endfloat 124 Qt uses a layout-based approach to widget management. Widgets are arranged in 125 the optimal positions in windows based on simple layout rules, leading to a 126 consistent look and feel. 127 128 Custom layouts can be used to provide more control over the positions and 129 sizes of child widgets. 130 131 \clearfloat 132 \section1 \l{Item Views Examples}{Item Views} 133 \beginfloatleft 134 \l{Item Views Examples}{\inlineimage itemview-examples.png 135 } 136 137 \endfloat 138 Item views are widgets that typically display data sets. Qt 4's model/view 139 framework lets you handle large data sets by separating the underlying data 140 from the way it is represented to the user, and provides support for 141 customized rendering through the use of delegates. 142 143 \clearfloat 144 \section1 \l{Graphics View Examples}{Graphics View} 145 \beginfloatleft 146 \l{Graphics View Examples}{\inlineimage graphicsview-examples.png 147 } 148 149 \endfloat 150 Qt is provided with a comprehensive canvas through the GraphicsView 151 classes. 152 153 \clearfloat 154 \section1 \l{Painting Examples}{Painting} 155 \beginfloatleft 156 \l{Painting Examples}{\inlineimage painting-examples.png 157 } 158 159 \endfloat 160 Qt's painting system is able to render vector graphics, images, and outline 161 font-based text with sub-pixel accuracy accuracy using anti-aliasing to 162 improve rendering quality. 163 164 \clearfloat 165 \section1 \l{Rich Text Examples}{Rich Text} 166 \beginfloatleft 167 \l{Rich Text Examples}{\inlineimage richtext-examples.png 168 } 169 170 \endfloat 171 Qt provides powerful document-oriented rich text engine that supports Unicode 172 and right-to-left scripts. Documents can be manipulated using a cursor-based 173 API, and their contents can be imported and exported as both HTML and in a 174 custom XML format. 175 176 \clearfloat 177 \section1 \l{Desktop Examples}{Desktop} 178 \beginfloatleft 179 \l{Desktop Examples}{\inlineimage desktop-examples.png 180 } 181 182 \endfloat 183 Qt provides features to enable applications to integrate with the user's 184 preferred desktop environment. 185 186 Features such as system tray icons, access to the desktop widget, and 187 support for desktop services can be used to improve the appearance of 188 applications and take advantage of underlying desktop facilities. 189 190 \clearfloat 191 \section1 \l{Drag and Drop Examples}{Drag and Drop} 192 \beginfloatleft 193 \l{Drag and Drop Examples}{\inlineimage draganddrop-examples.png 194 } 195 196 \endfloat 197 Qt supports native drag and drop on all platforms via an extensible 198 MIME-based system that enables applications to send data to each other in the 199 most appropriate formats. 200 201 Drag and drop can also be implemented for internal use by applications. 202 203 \clearfloat 204 \section1 \l{Threading and Concurrent Programming Examples}{Threading and Concurrent Programming} 205 \beginfloatleft 206 \l{Threading and Concurrent Programming Examples}{\inlineimage thread-examples.png 207 } 208 209 \endfloat 210 Qt 4 makes it easier than ever to write multithreaded applications. More 211 classes have been made usable from non-GUI threads, and the signals and slots 212 mechanism can now be used to communicate between threads. 213 214 The QtConcurrent namespace includes a collection of classes and functions 215 for straightforward concurrent programming. 216 217 \clearfloat 218 \section1 \l{Tools Examples}{Tools} 219 \beginfloatleft 220 \l{Tools Examples}{\inlineimage tool-examples.png 221 } 222 223 \endfloat 224 Qt is equipped with a range of capable tool classes, from containers and 225 iterators to classes for string handling and manipulation. 226 227 Other classes provide application infrastructure support, handling plugin 228 loading and managing configuration files. 229 230 \clearfloat 231 \section1 \l{Network Examples}{Network} 232 \beginfloatleft 233 \l{Network Examples}{\inlineimage network-examples.png 234 } 235 236 \endfloat 237 Qt is provided with an extensive set of network classes to support both 238 client-based and server side network programming. 239 240 \clearfloat 241 \section1 \l{Inter-Process Communication Examples}{Inter-Process Communication} 242 \beginfloatleft 243 \l{Inter-Process Communication Examples}{\inlineimage ipc-examples.png 244 } 245 246 \endfloat 247 Simple, lightweight inter-process communication can be performed using shared 248 memory and local sockets. 249 250 \clearfloat 251 \section1 \l{OpenGL Examples}{OpenGL} and \l{OpenVG Examples}{OpenVG} Examples 252 \beginfloatleft 253 \l{OpenGL Examples}{\inlineimage opengl-examples.png 254 } 255 256 \endfloat 257 Qt provides support for integration with OpenGL implementations on all 258 platforms, giving developers the opportunity to display hardware accelerated 259 3D graphics alongside a more conventional user interface. 260 261 Qt provides support for integration with OpenVG implementations on 262 platforms with suitable drivers. 263 264 \clearfloat 265 \section1 \l{Multimedia Examples}{Multimedia Framework} 266 \beginfloatleft 267 \l{Multimedia Examples}{\inlineimage phonon-examples.png 268 } 269 270 \endfloat 271 Qt provides low-level audio support on linux,windows and mac platforms by default and 272 an audio plugin API to allow developers to implement there own audio support for 273 custom devices and platforms. 274 275 The Phonon Multimedia Framework brings multimedia support to Qt applications. 276 277 \clearfloat 278 \section1 \l{SQL Examples}{SQL} 279 \beginfloatleft 280 \l{SQL Examples}{\inlineimage sql-examples.png 281 } 282 283 \endfloat 284 Qt provides extensive database interoperability, with support for products 285 from both open source and proprietary vendors. 286 287 SQL support is integrated with Qt's model/view architecture, making it easier 288 to provide GUI integration for your database applications. 289 290 \clearfloat 291 \section1 \l{XML Examples}{XML} 292 \beginfloatleft 293 \l{XML Examples}{\inlineimage xml-examples.png 294 } 295 296 \endfloat 297 XML parsing and handling is supported through SAX and DOM compliant APIs 298 as well as streaming classes. 299 300 The XQuery/XPath and XML Schema engines in the QtXmlPatterns modules 301 provide classes for querying XML files and custom data models. 302 303 \clearfloat 304 \section1 \l{Qt Designer Examples}{Qt Designer} 305 \beginfloatleft 306 \l{Qt Designer Examples}{\inlineimage designer-examples.png 307 } 308 309 \endfloat 310 Qt Designer is a capable graphical user interface designer that lets you 311 create and configure forms without writing code. GUIs created with 312 Qt Designer can be compiled into an application or created at run-time. 313 314 \clearfloat 315 \section1 \l{UiTools Examples}{UiTools} 316 \beginfloatleft 317 \l{UiTools Examples}{\inlineimage uitools-examples.png 318 } 319 320 \endfloat 321 User interfaces created with Qt Designer can be loaded and displayed at 322 run-time using the facilities of the QtUiTools module without the need 323 to generate code in advance. 324 325 \clearfloat 326 \section1 \l{Qt Linguist Examples}{Qt Linguist} 327 \beginfloatleft 328 \l{Qt Linguist Examples}{\inlineimage linguist-examples.png 329 } 330 331 \endfloat 332 Internationalization is a core feature of Qt. 333 334 \clearfloat 335 \section1 \l{Qt Script Examples}{Qt Script} 336 \beginfloatleft 337 \l{Qt Script Examples}{\inlineimage qtscript-examples.png 338 } 339 340 \endfloat 341 Qt is provided with a powerful embedded scripting environment through the QtScript 342 classes. 343 344 \clearfloat 345 \section1 \l{WebKit Examples}{WebKit} 346 \beginfloatleft 347 \l{WebKit Examples}{\inlineimage webkit-examples.png 348 } 349 350 \endfloat 351 Qt provides an integrated Web browser component based on WebKit, the popular 352 open source browser engine. 353 354 \clearfloat 355 \section1 \l{Help System Examples}{Help System} 356 \beginfloatleft 357 \l{Help System Examples}{\inlineimage assistant-examples.png 358 } 359 360 \endfloat 361 Support for interactive help is provided by the Qt Assistant application. 362 Developers can take advantages of the facilities it offers to display 363 specially-prepared documentation to users of their applications. 364 365 \clearfloat 366 \section1 \l{State Machine Examples}{State Machine} 367 \beginfloatleft 368 \l{State Machine Examples}{\inlineimage statemachine-examples.png 369 } 370 371 \endfloat 372 Qt provides a powerful hierarchical finite state machine through the Qt State 373 Machine classes. 374 375 \clearfloat 376 \section1 \l{Animation Framework Examples}{Animation Framework} 377 \beginfloatleft 378 \l{Animation Framework Examples}{\inlineimage animation-examples.png 379 } 380 381 \endfloat 382 These examples show to to use the \l{The Animation Framework}{animation framework} 383 to build highly animated, high-performance GUIs. 384 385 \clearfloat 386 \section1 \l{Multi-Touch Examples}{Multi-Touch Framework} 387 \beginfloatleft 388 \l{Multi-Touch Examples}{\inlineimage multitouch-examples.png 389 } 390 391 \endfloat 392 Support for multi-touch input makes it possible for developers to create 393 extensible and intuitive user interfaces. 394 395 \clearfloat 396 \section1 \l{Gestures Examples}{Gestures} 397 \beginfloatleft 398 \l{Gestures Examples}{\inlineimage gestures-examples.png 399 } 400 401 \endfloat 402 Applications can be written to respond to gestures as a natural input method. 403 These examples show how to enable support for standard and custom gestures in 404 applications. 405 406 \clearfloat 407 \section1 \l{D-Bus Examples}{D-Bus} 408 \beginfloatleft 409 \l{D-Bus Examples}{\inlineimage dbus-examples.png 410 } 411 412 \endfloat 413 Systems with limited resources, specialized hardware, and small 414 screens require special attention. 415 416 \clearfloat 417 \section1 \l{Qt for Embedded Linux Examples}{Qt for Embedded Linux} 418 \beginfloatleft 419 \l{Qt for Embedded Linux Examples}{\inlineimage qt-embedded-examples.png 420 } 421 422 \endfloat 423 D-Bus is an inter-process communication protocol for Unix/Linux systems. 424 These examples demonstrate how to write application that communicate with 425 each other. 426 427 \clearfloat 428 \section1 \l{ActiveQt Examples}{ActiveQt} 429 \beginfloatleft 430 \l{ActiveQt Examples}{\inlineimage activeqt-examples.png 431 } 432 433 \endfloat 434 These examples demonstrate how to write ActiveX controls and control servers 435 with Qt, and how to use ActiveX controls and COM objects in a Qt application. 436 437 \clearfloat 438 \section1 \l{Qt Quarterly}{Qt Quarterly} 439 \beginfloatleft 440 \l{Qt Quarterly}{\inlineimage qq-thumbnail.png 441 } 442 443 \endfloat 444 One more valuable source for examples and explanations of Qt 445 features is the archive of \l{Qt Quarterly}, a newsletter for 446 Qt developers. 447 448 \clearfloat 29 \group all-examples 30 \title Qt Examples 31 32 Qt includes a set of examples that cover nearly every aspect of Qt 33 development. They aren't meant to be impressive when you run them, 34 but in each case the source code has been carefully written to 35 illustrate one or more best Qt programming practices. 36 37 You can run the examples from the \l{Examples and Demos Launcher} 38 application (except see \l{QML Examples and Demos} {QML Examples} 39 for special instructions for running those examples). 40 41 The examples are listed below by functional area. Each example 42 listed in a particular functional area is meant to illustrate how 43 best to use Qt to do some particular task in that functional area, 44 but the examples will often use features from other functional 45 areas as well for completeness. 46 47 If you are new to Qt, you should probably start by going through 48 the \l{Tutorials}, and then begin with the 49 \l{mainwindows/application} {Application} example. 50 51 In addition to these examples and the \l{Tutorials}{tutorials}, Qt 52 includes a \l{Qt Demonstrations}{selection of demos} that 53 deliberately show off Qt's features. You might want to look at 54 these as well. 55 56 These examples are provided under the terms of the 57 \l{New and Modified BSD Licenses}{Modified BSD License}. 58 59 60 \section1 Examples by Functional Area 61 62 \generatelist{related} 449 63 */ 450 64 451 65 /*! 452 66 \page examples-widgets.html 453 \title Widgets Examples 454 455 \contentspage Qt Examples 456 \nextpage Dialog Examples 67 \title Widget Examples 68 \ingroup all-examples 69 \brief Lots of examples of how to use different kinds of widgets. 457 70 458 71 \image widget-examples.png … … 500 113 /*! 501 114 \page examples-dialogs.html 115 \ingroup all-examples 502 116 \title Dialog Examples 503 504 \previouspage Widgets Examples 505 \contentspage Qt Examples 506 \nextpage Main Window Examples 117 \brief Using Qt's standard dialogs and building and using custom dialogs. 507 118 508 119 \image dialog-examples.png … … 530 141 /*! 531 142 \page examples-mainwindow.html 143 \ingroup all-examples 532 144 \title Main Window Examples 533 534 \previouspage Dialog Examples 535 \contentspage Qt Examples 536 \nextpage Layout Examples 145 \brief Building applications around a main window. 537 146 538 147 \image mainwindow-examples.png … … 558 167 /*! 559 168 \page examples-layouts.html 169 \ingroup all-examples 560 170 \title Layout Examples 561 562 \previouspage Main Window Examples 563 \contentspage Qt Examples 564 \nextpage Item Views Examples 171 \brief Using Qt's layout-based approach to widget management. 565 172 566 173 \image layout-examples.png … … 585 192 /*! 586 193 \page examples-itemviews.html 194 \ingroup all-examples 587 195 \title Item Views Examples 588 589 \previouspage Layout Examples 590 \contentspage Qt Examples 591 \nextpage Graphics View Examples 196 \brief Using the model/view design pattern to separate presentation from data. 592 197 593 198 \image itemview-examples.png … … 623 228 /*! 624 229 \page examples-graphicsview.html 230 \ingroup all-examples 625 231 \title Graphics View Examples 626 627 \previouspage Item Views Examples 628 \contentspage Qt Examples 629 \nextpage Painting Examples 232 \brief Using Qt to manage and interact with a large (potentially) number of graphics items. 630 233 631 234 \image graphicsview-examples.png … … 640 243 \o \l{graphicsview/collidingmice}{Colliding Mice}\raisedaster 641 244 \o \l{graphicsview/diagramscene}{Diagram Scene}\raisedaster 642 \o \l{graphicsview/dragdroprobot}{Drag and Drop Robot} 643 \o \l{graphicsview/elasticnodes}{Elastic Nodes} 245 \o \l{graphicsview/dragdroprobot}{Drag and Drop Robot}\raisedaster 246 \o \l{graphicsview/elasticnodes}{Elastic Nodes}\raisedaster 247 \o \l{graphicsview/padnavigator}{Pad Navigator}\raisedaster 644 248 \o \l{graphicsview/portedasteroids}{Ported Asteroids} 645 249 \o \l{graphicsview/portedcanvas}{Ported Canvas} … … 653 257 \o \l{graphicsview/simpleanchorlayout}{Simple Anchor Layout} 654 258 \o \l{graphicsview/weatheranchorlayout}{Weather Anchor Layout} 259 \o \l{graphicsview/basicgraphicslayouts}{Basic Graphics Layouts} 655 260 \endlist 656 261 … … 668 273 /*! 669 274 \page examples-painting.html 275 \ingroup all-examples 670 276 \title Painting Examples 671 672 \previouspage Graphics View Examples 673 \contentspage Qt Examples 674 \nextpage Rich Text Examples 277 \brief How to use the Qt painting system. 675 278 676 279 \image painting-examples.png … … 700 303 /*! 701 304 \page examples-richtext.html 305 \ingroup all-examples 702 306 \title Rich Text Examples 703 704 \previouspage Painting Examples 705 \contentspage Qt Examples 706 \nextpage Desktop Examples 307 \brief Using the document-oriented rich text engine. 707 308 708 309 \image richtext-examples.png … … 723 324 /*! 724 325 \page examples-desktop.html 326 \ingroup all-examples 725 327 \title Desktop Examples 726 727 \previouspage Rich Text Examples 728 \contentspage Qt Examples 729 \nextpage Drag and Drop Examples 328 \brief Integrating your Qt application with your favorite desktop. 730 329 731 330 \image desktop-examples.png … … 746 345 /*! 747 346 \page examples-draganddrop.html 347 \ingroup all-examples 748 348 \title Drag and Drop Examples 749 750 \previouspage Desktop Examples 751 \contentspage Qt Examples 752 \nextpage Threading and Concurrent Programming Examples 349 \brief How to access your platform's native drag and drop functionality. 753 350 754 351 \image draganddrop-examples.png … … 774 371 /*! 775 372 \page examples-threadandconcurrent.html 373 \ingroup all-examples 776 374 \title Threading and Concurrent Programming Examples 777 778 \previouspage Drag and Drop Examples 779 \contentspage Qt Examples 780 \nextpage Tools Examples 375 \brief Threading and concurrent programming in Qt. 781 376 782 377 \image thread-examples.png … … 814 409 /*! 815 410 \page examples.tools.html 411 \ingroup all-examples 816 412 \title Tools Examples 817 818 \previouspage Threading and Concurrent Programming Examples 819 \contentspage Qt Examples 820 \nextpage Network Examples 413 \brief Using Qt's containers, iterators, and other tool classes. 821 414 822 415 \image tool-examples.png … … 852 445 /*! 853 446 \page examples-network.html 447 \ingroup all-examples 854 448 \title Network Examples 855 856 \previouspage Tools Examples 857 \contentspage Qt Examples 858 \nextpage Inter-Process Communication Examples 449 \brief How to do network programming in Qt. 859 450 860 451 \image network-examples.png … … 881 472 \o \l{network/torrent}{Torrent} 882 473 \o \l{network/googlesuggest}{Google Suggest} 474 \o \l{network/bearercloud}{Bearer Cloud}\raisedaster 475 \o \l{network/bearermonitor}{Bearer Monitor} 476 \o \l{network/securesocketclient}{Secure Socket Client} 883 477 \endlist 884 478 … … 888 482 /*! 889 483 \page examples-ipc.html 890 \title Inter-Process Communication Examples 891 892 \previouspage Network Examples 893 \contentspage Qt Examples 894 \nextpage OpenGL Examples 484 \ingroup all-examples 485 \title IPC Examples 486 \brief Inter-Process Communication with Qt. 895 487 896 488 \image ipc-examples.png … … 905 497 /*! 906 498 \page examples-opengl.html 499 \ingroup all-examples 907 500 \title OpenGL Examples 908 909 \previouspage Inter-Process Communication Examples 910 \contentspage Qt Examples 911 \nextpage OpenVG Examples 501 \brief Accessing OpenGL from Qt. 912 502 913 503 \image opengl-examples.png … … 939 529 /*! 940 530 \page examples-openvg.html 531 \ingroup all-examples 941 532 \title OpenVG Examples 942 943 \previouspage OpenGL Examples 944 \contentspage Qt Examples 945 \nextpage Multimedia Examples 946 947 \image openvg-examples.png 533 \brief Accessing OpenVG from Qt. 534 535 \image opengl-examples.png 948 536 949 537 Qt provides support for integration with OpenVG implementations on … … 960 548 /*! 961 549 \page examples-multimedia.html 550 \ingroup all-examples 962 551 \title Multimedia Examples 963 964 \previouspage OpenGL Examples 965 \contentspage Qt Examples 966 \nextpage SQL Examples 552 \brief Audio, video, and Phonon with Qt. 967 553 968 554 \image phonon-examples.png … … 1009 595 /*! 1010 596 \page examples-sql.html 597 \ingroup all-examples 1011 598 \title SQL Examples 1012 1013 \previouspage Multimedia Examples 1014 \contentspage Qt Examples 1015 \nextpage XML Examples 599 \brief Accessing your SQL database from Qt. 1016 600 1017 601 \image sql-examples.png … … 1029 613 \o \l{sql/relationaltablemodel}{Relational Table Model} 1030 614 \o \l{sql/tablemodel}{Table Model} 615 \o \l{sql/masterdetail}{Master Detail} 1031 616 \o \l{sql/sqlwidgetmapper}{SQL Widget Mapper}\raisedaster 1032 617 \endlist … … 1038 623 /*! 1039 624 \page examples-xml.html 625 \ingroup all-examples 1040 626 \title XML Examples 1041 1042 \previouspage SQL Examples 1043 \contentspage Qt Examples 1044 \nextpage Qt Designer Examples 627 \brief Using XML with Qt. 1045 628 1046 629 \image xml-examples.png XML … … 1055 638 \o \l{xml/rsslisting}{RSS-Listing} 1056 639 \o \l{xml/xmlstreamlint}{XML Stream Lint Example}\raisedaster 640 \o \l{xml/htmlinfo}{XML HTML Info} 1057 641 \endlist 1058 642 … … 1074 658 /*! 1075 659 \page examples-designer.html 660 \ingroup all-examples 1076 661 \title Qt Designer Examples 1077 1078 \previouspage XML Examples 1079 \contentspage Qt Examples 1080 \nextpage UiTools Examples 662 \brief Using Qt Designer to build your UI. 1081 663 1082 664 \image designer-examples.png QtDesigner … … 1099 681 /*! 1100 682 \page examples-uitools.html 683 \ingroup all-examples 1101 684 \title UiTools Examples 1102 1103 \previouspage Qt Designer Examples 1104 \contentspage Qt Examples 1105 \nextpage Qt Linguist Examples 685 \brief Using the QtUiTools module. 1106 686 1107 687 \image uitools-examples.png UiTools … … 1115 695 /*! 1116 696 \page examples-linguist.html 697 \ingroup all-examples 1117 698 \title Qt Linguist Examples 1118 1119 \previouspage UiTools Examples 1120 \contentspage Qt Examples 1121 \nextpage Qt Script Examples 699 \brief Using Qt Linguist to internationalize your Qt application. 1122 700 1123 701 \image linguist-examples.png … … 1135 713 /*! 1136 714 \page examples-script.html 715 \ingroup all-examples 1137 716 \title Qt Script Examples 1138 1139 \previouspage Qt Linguist Examples 1140 \contentspage Qt Examples 1141 \nextpage WebKit Examples 717 \brief Using the Qt scripting environment. 1142 718 1143 719 \image qtscript-examples.png QtScript … … 1164 740 /*! 1165 741 \page examples-webkit.html 742 \ingroup all-examples 1166 743 \title WebKit Examples 1167 1168 \previouspage Qt Script Examples 1169 \contentspage Qt Examples 1170 \nextpage Help System Examples 744 \brief Using WebKit in your Qt application. 1171 745 1172 746 \image webkit-examples.png WebKit … … 1192 766 \o A real-world example that shows how an existing Web-based service can be accessed 1193 767 using QtWebKit. 768 \row \o \l{webkit/imageanalyzer}{Image Analyzer}\raisedaster 769 \o A \l{The QtWebKit Bridge}{QtWebKit bridge} application which contains a 770 web interface and client-side processing. 1194 771 \row \o \l{webkit/previewer}{Previewer}\raisedaster 1195 772 \o Shows how to make a simple Web page previewer by using Qt's text input widgets … … 1205 782 /*! 1206 783 \page examples-helpsystem.html 784 \ingroup all-examples 1207 785 \title Help System Examples 1208 1209 \previouspage WebKit Examples 1210 \contentspage Qt Examples 1211 \nextpage State Machine Examples 786 \brief Adding interactive help to your Qt application. 1212 787 1213 788 \image assistant-examples.png HelpSystem … … 1219 794 \list 1220 795 \o \l{help/simpletextviewer}{Simple Text Viewer}\raisedaster 796 \o \l{help/remotecontrol}{Remote Control} 797 \o \l{help/contextsensitivehelp}{Context-Sensitive Help} 1221 798 \endlist 1222 799 … … 1226 803 /*! 1227 804 \page examples-statemachine.html 805 \ingroup all-examples 1228 806 \title State Machine Examples 1229 1230 \previouspage Help System Examples 1231 \contentspage Qt Examples 1232 \nextpage Animation Framework Examples 807 \brief Using Qt's finite state machine classes. 1233 808 1234 809 \image statemachine-examples.png StateMachine … … 1252 827 /*! 1253 828 \page examples-animation.html 829 \ingroup all-examples 1254 830 \title Animation Framework Examples 1255 1256 \previouspage State Machine Examples 1257 \contentspage Qt Examples 1258 \nextpage Multi-Touch Examples 831 \brief Doing animations with Qt. 1259 832 1260 833 \image animation-examples.png Animation … … 1273 846 1274 847 /*! 1275 \page examples-multitouch.html 1276 \title Multi-Touch Examples 1277 1278 \previouspage Animation Framework Examples 1279 \contentspage Qt Examples 1280 \nextpage Gestures Examples 1281 1282 Support for multi-touch input makes it possible for developers to create 848 \page examples-touch.html 849 \ingroup all-examples 850 \title Touch Input Examples 851 \brief Using Qt's touch input capability. 852 853 Support for touch input makes it possible for developers to create 1283 854 extensible and intuitive user interfaces. 1284 855 1285 856 \list 1286 \o \l{ multitouch/dials}{Multi-Touch Dials}1287 \o \l{ multitouch/fingerpaint}{Finger Paint}1288 \o \l{ multitouch/knobs}{Multi-Touch Knobs}1289 \o \l{ multitouch/pinchzoom}{Pinch Zoom}857 \o \l{touch/dials}{Touch Dials} 858 \o \l{touch/fingerpaint}{Finger Paint} 859 \o \l{touch/knobs}{Touch Knobs} 860 \o \l{touch/pinchzoom}{Pinch Zoom} 1290 861 \endlist 1291 862 */ … … 1293 864 /*! 1294 865 \page examples-gestures.html 866 \ingroup all-examples 1295 867 \title Gestures Examples 1296 1297 \previouspage Multi-Touch Examples 1298 \contentspage Qt Examples 1299 \nextpage D-Bus Examples 868 \brief Gesture programming examples. 1300 869 1301 870 The API of the gesture framework is not yet finalized and … … 1309 878 /*! 1310 879 \page examples-dbus.html 880 \ingroup all-examples 1311 881 \title D-Bus Examples 1312 1313 \previouspage Gestures Examples 1314 \contentspage Qt Examples 1315 \nextpage Qt for Embedded Linux Examples 882 \brief Using D-Bus from Qt applications. 1316 883 1317 884 \list … … 1320 887 \o \l{dbus/listnames}{List Names} 1321 888 \o \l{dbus/pingpong}{Ping Pong} 1322 \o \l{dbus/remotecontrolledcar}{Remote Controlled Car} 889 \o \l{dbus/remotecontrolledcar}{Remote Controlled Car} 1323 890 \endlist 1324 891 … … 1328 895 /*! 1329 896 \page examples-embeddedlinux.html 897 \ingroup all-examples 1330 898 \title Qt for Embedded Linux Examples 1331 1332 \previouspage D-Bus Examples 1333 \contentspage Qt Examples 1334 \nextpage ActiveQt Examples 899 \brief Using Qt in Embedded Linux. 1335 900 1336 901 \image qt-embedded-examples.png QtEmbedded … … 1350 915 /*! 1351 916 \page examples-activeqt.html 917 \ingroup all-examples 1352 918 \title ActiveQt Examples 1353 1354 \previouspage Qt for Embedded Linux Examples 1355 \contentspage Qt Examples 1356 \nextpage Qt Quarterly 919 \brief Using ActiveX from Qt applications. 1357 920 1358 921 \image activeqt-examples.png ActiveQt -
trunk/doc/src/getting-started/how-to-learn-qt.qdoc
r651 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 60 46 read at least the first few chapters of the \l{Qt Designer manual}. 61 47 62 By now you'll have produced some small working applications and have a63 broad feel for Qt programming. You could start work on your own64 projects straight away, but we recommend reading a couple of key65 overviews to deepen your understanding of Qt: \l{Qt Object Model}66 and \l{Signals and Slots}.48 By now you'll have produced some small working applications and 49 have a broad feel for Qt programming. You could start work on your 50 own projects straight away, but we recommend reading a couple of 51 key overviews to deepen your understanding of Qt: The Qt \l{Object 52 Model} and \l{Signals and Slots}. 67 53 68 54 \beginfloatleft -
trunk/doc/src/getting-started/installation.qdoc
r769 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 45 31 \brief Installing Qt on supported platforms. 46 32 47 The installation procedure is different on each Qt platform. 48 Please follow the instructions for your platform from the following list. 33 The installation procedure is different on each Qt platform. This page provides 34 information on how to install Qt, as well as software and hardware requirements 35 for using Qt on each of the supported platforms. Please follow the instructions 36 for your platform from the following list. 49 37 50 38 \generatelist{related} 39 51 40 */ 52 41 53 42 /*! \page install-x11.html 54 \title Installing Qt onX11 Platforms43 \title Installing Qt for X11 Platforms 55 44 \ingroup installation 56 45 \brief How to install Qt on platforms with X11. 57 46 \previouspage Installation 58 47 59 \note Qt for X11 has some requirements that are given in more detail 60 in the \l{Qt for X11 Requirements} document. 61 62 \list 1 63 \o If you have the commercial edition of Qt, install your license 48 \tableofcontents 49 50 Qt for X11 has some requirements that are given in more detail 51 in the \l{Qt for X11 Requirements} document. 52 53 \section1 Step 1: Installing the License File (commercial editions only) 54 If you have the commercial edition of Qt, install your license 64 55 file as \c{$HOME/.qt-license}. 65 56 66 57 For the open source version you do not need a license file. 67 58 68 \o Unpack the archive if you have not done so already. For example, 69 if you have the \c{qt-everywhere-opensource-src-4.6.3.tar.gz} 59 \section1 Step 2: Unpacking the Archive 60 Unpack the archive if you have not done so already. For example, 61 if you have the \c{qt-everywhere-opensource-src-4.7.2.tar.gz} 70 62 package, type the following commands at a command line prompt: 71 63 72 64 \snippet doc/src/snippets/code/doc_src_installation.qdoc 0 73 65 74 This creates the directory \c{/tmp/qt-everywhere-opensource-src-4. 6.3}66 This creates the directory \c{/tmp/qt-everywhere-opensource-src-4.7.2} 75 67 containing the files from the archive. We only support the GNU version of 76 68 the tar archiving utility. Note that on some systems it is called gtar. 77 69 78 \ o Building70 \section1 Step 3: Building the Library 79 71 80 72 To configure the Qt library for your machine type, run the … … 82 74 83 75 By default, Qt is configured for installation in the 84 \c{/usr/local/Trolltech/Qt-4. 6.3} directory, but this can be76 \c{/usr/local/Trolltech/Qt-4.7.2} directory, but this can be 85 77 changed by using the \c{-prefix} option. 86 78 … … 96 88 If \c{-prefix} is outside the build directory, you need to install 97 89 the library, demos, examples, tools, and tutorials in the appropriate 98 place. To do this , type:90 place. To do this (as root if necessary), type: 99 91 100 92 \snippet doc/src/snippets/code/doc_src_installation.qdoc 3 101 102 , as root if necessary. 103 93 104 94 Note that on some systems the make utility is named differently, 105 95 e.g. gmake. The configure script tells you which make utility to … … 111 101 before running \c configure again. 112 102 113 \ o Environment variables103 \section1 Step 4: Set the Environment Variables 114 104 115 105 In order to use Qt, some environment variables needs to be … … 134 124 For compilers that do not support rpath you must also extended the 135 125 \c LD_LIBRARY_PATH environment variable to include 136 \c{/usr/local/Trolltech/Qt-4. 6.3/lib}. On Linux with GCC this step126 \c{/usr/local/Trolltech/Qt-4.7.2/lib}. On Linux with GCC this step 137 127 is not needed. 138 128 139 \o That's all. Qt is now installed. 129 \bold {That's all. Qt is now installed.} 130 131 \section1 Qt Demos and Examples 140 132 141 133 If you are new to Qt, we suggest that you take a look at the demos … … 153 145 \o \l{Deploying Qt Applications} 154 146 \endlist 155 \endlist156 147 157 148 We hope you will enjoy using Qt. Good luck! … … 161 152 /*! 162 153 \page install-win.html 163 \title Installing Qt onWindows154 \title Installing Qt for Windows 164 155 \ingroup installation 165 156 \brief How to install Qt on Windows. 166 157 \previouspage Installation 167 158 168 \note Qt for Windows has some requirements that are given in more detail 169 in the \l{Qt for Windows Requirements} document. 170 171 \table 172 \row \o \bold{Notes:} 173 \list 174 \o If you have obtained a binary package for this platform, 175 consult the installation instructions provided instead of the ones in 176 this document. 177 \o \l{Open Source Versions of Qt} is not officially supported for use with 178 any version of Visual Studio. Integration with Visual Studio is available 179 as part of the \l{Qt Commercial Editions}. 180 181 \endlist 182 \endtable 183 184 \list 1 185 \o If you have the commercial edition of Qt, copy the license file 159 \tableofcontents 160 161 Qt for Windows has some requirements that are given in more detail 162 in the \l{Qt for Windows Requirements} document. 163 164 If you have obtained a binary package for this platform, 165 consult the installation instructions provided instead of the ones in 166 this document. 167 168 Open Source Versions of Qt is not officially supported for use with 169 any version of Visual Studio. Integration with Visual Studio is available 170 as part of the \l{Qt Commercial Edition}. 171 172 \section1 Step 1: Install the License File (commercial editions only) 173 174 If you have the commercial edition of Qt, copy the license file 186 175 from your account on dist.trolltech.com into your home directory 187 176 (this may be known as the \c userprofile environment variable) and … … 193 182 For the open source version you do not need a license file. 194 183 195 \o Uncompress the files into the directory you want Qt installed; 196 e.g. \c{C:\Qt\4.6.3}. 184 \section1 Step 2: Unpack the Archive 185 186 Uncompress the files into the directory you want Qt installed; 187 e.g. \c{C:\Qt\4.7.2}. 197 188 198 189 \note The install path must not contain any spaces or Windows specific 199 190 file system characters. 200 191 201 \ oEnvironment variables192 \section1 Step 3: Set the Environment variables 202 193 203 194 In order to build and use Qt, the \c PATH environment variable needs to be … … 206 197 \snippet doc/src/snippets/code/doc_src_installation.qdoc 7 207 198 208 This is done by adding \c{c:\Qt\4. 6.3\bin} to the \c PATH variable.199 This is done by adding \c{c:\Qt\4.7.2\bin} to the \c PATH variable. 209 200 210 201 For newer versions of Windows, \c PATH can be extended through … … 215 206 on your choice of software development environment. 216 207 217 \ bold{Note}:If you don't use the configured shells, which is208 \note If you don't use the configured shells, which is 218 209 available in the application menu, in the \l{Open Source Versions of Qt}, 219 210 \c configure requires that \c sh.exe is not in the path 220 211 or that it is run from \c msys. This also goes for mingw32-make. 221 212 222 \o Building 213 \section1 Step 4: Build the Qt Library 214 223 215 224 216 To configure the Qt library for your machine, type the following command … … 255 247 before running \c configure again. 256 248 257 \o That's all. Qt is now installed. 249 \bold{That's all. Qt is now installed.} 250 251 \section1 Qt Demos and Examples 258 252 259 253 If you are new to Qt, we suggest that you take a look at the demos … … 271 265 \endlist 272 266 273 \endlist274 275 267 We hope you will enjoy using Qt. Good luck! 276 268 … … 278 270 279 271 /*! \page install-mac.html 280 \title Installing Qt onMac OS X272 \title Installing Qt for Mac OS X 281 273 \ingroup installation 282 274 \brief How to install Qt on Mac OS X. 283 275 \previouspage Installation 284 285 \note Qt for Mac OS X has some requirements that are given in more detail 276 \tableofcontents 277 278 Qt for Mac OS X has some requirements that are given in more detail 286 279 in the \l{Qt for Mac OS X Requirements} document. 287 280 288 \bold{Note for the binary package}: If you have the binary package, simply double-click on the Qt.mpkg 281 The following instructions describe how to install Qt from the source package. 282 283 For the binary package, simply double-click on the Qt.mpkg 289 284 and follow the instructions to install Qt. You can later run the \c{uninstall-qt.py} 290 285 script to uninstall the binary package. The script is located in /Developer/Tools and 291 286 must be run as root. 292 287 293 The following instructions describe how to install Qt from the source package. 294 295 \list 1 296 \o If you have the commercial edition of Qt, install your license 288 \note Do not run the iPhone simulator while installing Qt. The 289 \l{http://openradar.appspot.com/7214991} 290 {iPhone simulator conflicts with the package installer}. 291 292 \section1 Step 1: Install the License File (commercial editions only) 293 If you have the commercial edition of Qt, install your license 297 294 file as \c{$HOME/.qt-license}. 298 295 299 296 For the open source version you do not need a license file. 300 297 301 \oUnpack the archive if you have not done so already. For example,302 if you have the \c{qt-everywhere-opensource-src-4. 6.3.tar.gz}298 Unpack the archive if you have not done so already. For example, 299 if you have the \c{qt-everywhere-opensource-src-4.7.2.tar.gz} 303 300 package, type the following commands at a command line prompt: 304 301 305 302 \snippet doc/src/snippets/code/doc_src_installation.qdoc 11 306 303 307 This creates the directory \c{/tmp/qt-everywhere-opensource-src-4. 6.3}304 This creates the directory \c{/tmp/qt-everywhere-opensource-src-4.7.2} 308 305 containing the files from the archive. 309 306 310 \ o Building307 \section1 Step 2: Build the Qt Library 311 308 312 309 To configure the Qt library for your machine type, run the … … 314 311 315 312 By default, Qt is configured for installation in the 316 \c{/usr/local/Trolltech/Qt-4. 6.3} directory, but this can be313 \c{/usr/local/Trolltech/Qt-4.7.2} directory, but this can be 317 314 changed by using the \c{-prefix} option. 318 315 … … 343 340 \snippet doc/src/snippets/code/doc_src_installation.qdoc 14 344 341 345 as root, if neccessary (note that thisrequires that you have administrator access346 to your machine).347 348 There is a potential race condition when running make install with multiple342 This command requires that you have administrator access 343 on your machine. 344 345 \note There is a potential race condition when running make install with multiple 349 346 jobs. It is best to only run one make job (-j1) for the install. 350 347 351 \bold{Note:}If you later need to reconfigure and rebuild Qt from the348 If you later need to reconfigure and rebuild Qt from the 352 349 same location, ensure that all traces of the previous configuration are 353 350 removed by entering the build directory and typing \c{make confclean} 354 351 before running \c configure again. 355 352 356 \ oEnvironment variables353 \section1 Step 3: Set the Environment variables 357 354 358 355 In order to use Qt, some environment variables need to be … … 374 371 variables accordingly. 375 372 376 \o That's all. Qt is now installed. 377 373 \bold {That's all. Qt is now installed.} 374 375 \section1 Qt Demos and Examples 378 376 If you are new to Qt, we suggest that you take a look at the demos 379 377 and examples to see Qt in action. Run the Qt Examples and Demos … … 389 387 \o \l{Deploying Qt Applications} 390 388 \endlist 391 \endlist392 389 393 390 We hope you will enjoy using Qt. Good luck! … … 396 393 397 394 /*! \page install-wince.html 398 \title Installing Qt onWindows CE395 \title Installing Qt for Windows CE 399 396 \ingroup installation 400 397 \ingroup qtce 401 \brief How to install Qt onWindows CE.398 \brief How to install Qt for Windows CE. 402 399 \previouspage Installation 403 404 \note Qt for Windows CE has some requirements that are given in more detail 400 \tableofcontents 401 402 Qt for Windows CE has some requirements that are given in more detail 405 403 in the \l{Qt for Windows CE Requirements} document. 406 404 407 \list 1 408 \o Uncompress the files into the directory you want to install Qt into; 409 e.g., \c{C:\Qt\4.6.3}. 410 411 \note The install path must not contain any spaces. 412 413 \o Environment variables 414 415 In order to build and use Qt, the \c PATH environment variable needs 416 to be extended: 417 418 \snippet doc/src/snippets/code/doc_src_installation.qdoc 18 419 420 This is done by adding \c{c:\Qt\4.6.3\bin} to the \c PATH variable. 421 422 For newer versions of Windows, \c PATH can be extended through 423 "Control Panel->System->Advanced->Environment variables" and for 424 older versions by editing \c{c:\autoexec.bat}. 425 426 Make sure the enviroment variables for your compiler are set. 427 Visual Studio includes \c{vcvars32.bat} for that purpose - or simply 428 use the "Visual Studio Command Prompt" from the Start menu. 429 430 \o Configuring Qt 431 432 To configure Qt for Windows Mobile 5.0 for Pocket PC, type the 433 following: 434 435 \snippet doc/src/snippets/code/doc_src_installation.qdoc 19 436 437 If you want to configure Qt for another platform or with other 438 options, type \c{configure -help} to get a list of all available 439 options. See the \c README file for the list of supported platforms. 440 441 442 \o Building Qt 443 444 Now, to build Qt you first have to update your \c PATH, \c INCLUDE 445 and \c LIB paths to point to the correct resources for your target 446 platforms. For a default installation of the Windows Mobile 5.0 447 Pocket PC SDK, this is done with the following commands: 448 449 \snippet doc/src/snippets/code/doc_src_installation.qdoc 20 450 451 We provide a convenience script for this purpose, called \c{setcepaths}. 452 Simply type: 453 454 \snippet doc/src/snippets/code/doc_src_installation.qdoc 21 455 456 Then to build Qt type: 457 458 \snippet doc/src/snippets/code/doc_src_installation.qdoc 22 459 460 \o That's all. Qt is now installed. 461 462 To get started with Qt, you can check out the examples found in the 463 \c{examples} directory of your Qt installation. The documentation can 464 be found in \c{doc\html}. 465 466 \bold{Remember:} If you reconfigure Qt for a different platform, 467 make sure you start with a new clean console to get rid of the 468 platform dependent include directories. 469 470 The links below provide further information for using Qt: 471 \list 472 \o \l{How to Learn Qt} 473 \o \l{Tutorials} 474 \o \l{Developer Zone} 475 \o \l{Deploying Qt Applications} 476 \endlist 477 478 You might also want to try the following Windows CE specific links: 479 \list 480 \o \l{Windows CE - Introduction to using Qt} 481 \o \l{Windows CE - Working with Custom SDKs} 482 \o \l{Windows CE - Using shadow builds} 483 \o \l{Windows CE - Signing} 484 \endlist 485 486 Information on feature and performance tuning for embedded builds can 487 be found on the following pages: 488 \list 489 \o \l{Fine-Tuning Features in Qt} 490 \o \l{Qt Performance Tuning} 491 \endlist 492 \endlist 405 \section1 Step 1: Install the License File (commercial editions only) 406 Uncompress the files into the directory you want to install Qt into; 407 e.g., \c{C:\Qt\4.7.2}. 408 409 \note The install path must not contain any spaces. 410 411 \section1 Step 2: Set the Environment variables 412 413 In order to build and use Qt, the \c PATH environment variable needs 414 to be extended: 415 416 \snippet doc/src/snippets/code/doc_src_installation.qdoc 18 417 This is done by adding \c{c:\Qt\4.7.2\bin} to the \c PATH variable. 418 419 For newer versions of Windows, \c PATH can be extended through 420 "Control Panel->System->Advanced->Environment variables" and for 421 older versions by editing \c{c:\autoexec.bat}. 422 423 Make sure the enviroment variables for your compiler are set. 424 Visual Studio includes \c{vcvars32.bat} for that purpose - or simply 425 use the "Visual Studio Command Prompt" from the Start menu. 426 427 \section1 Step 3: Configure Qt 428 429 To configure Qt for Windows Mobile 5.0 for Pocket PC, type the 430 following: 431 432 \snippet doc/src/snippets/code/doc_src_installation.qdoc 19 433 434 If you want to configure Qt for another platform or with other 435 options, type \c{configure -help} to get a list of all available 436 options. See the \c README file for the list of supported platforms. 437 438 \section1 Step 4: Build Qt Library 439 440 Now, to build Qt you first have to update your \c PATH, \c INCLUDE 441 and \c LIB paths to point to the correct resources for your target 442 platforms. For a default installation of the Windows Mobile 5.0 443 Pocket PC SDK, this is done with the following commands: 444 445 \snippet doc/src/snippets/code/doc_src_installation.qdoc 20 446 447 We provide a convenience script for this purpose, called \c{setcepaths}. 448 Simply type: 449 450 \snippet doc/src/snippets/code/doc_src_installation.qdoc 21 451 452 Then to build Qt type: 453 454 \snippet doc/src/snippets/code/doc_src_installation.qdoc 22 455 456 \bold{That's all. Qt is now installed.} 457 458 \section1 Qt Demos and Examples 459 460 To get started with Qt, you can check out the examples found in the 461 \c{examples} directory of your Qt installation. The documentation can 462 be found in \c{doc\html}. 463 464 \note If you reconfigure Qt for a different platform, 465 make sure you start with a new clean console to get rid of the 466 platform dependent include directories. 467 468 The links below provide further information for using Qt: 469 \list 470 \o \l{How to Learn Qt} 471 \o \l{Tutorials} 472 \o \l{Developer Zone} 473 \o \l{Deploying Qt Applications} 474 \endlist 475 476 You might also want to try the following Windows CE specific links: 477 \list 478 \o \l{Windows CE - Introduction to using Qt} 479 \o \l{Windows CE - Working with Custom SDKs} 480 \o \l{Windows CE - Using shadow builds} 481 \o \l{Windows CE - Signing} 482 \endlist 483 484 Information on feature and performance tuning for embedded builds can 485 be found on the following pages: 486 \list 487 \o \l{Fine-Tuning Features in Qt} 488 \o \l{Qt Performance Tuning} 489 \endlist 493 490 494 491 We hope you will enjoy using Qt. Good luck! … … 496 493 497 494 /*! \page install-Symbian-installer.html 498 \title Installing Qt onthe Symbian platform from a Binary Package495 \title Installing Qt for the Symbian platform from a Binary Package 499 496 \ingroup qtsymbian 500 \brief How to install Qt on the Symbian platform from a binary package. 501 502 \note Qt for the Symbian platform has some requirements that are given in more detail 497 \brief How to install Qt for the Symbian platform from a binary package. 498 \previouspage Installation 499 500 \tableofcontents 501 502 Qt for the Symbian platform has some requirements that are given in more detail 503 503 in the \l{Qt for the Symbian platform Requirements} document. 504 504 505 \list 1 506 507 \o Install Qt 508 509 Run \c{qt-symbian-opensource-4.6.3.exe} and follow the instructions. 505 506 \section1 Step 1: Install Qt 507 508 Run \c{qt-symbian-opensource-4.7.2.exe} and follow the instructions. 510 509 511 510 \note Qt must be installed on the same drive as the Symbian SDK you are 512 511 using, and the install path must not contain any spaces. 513 512 514 \oInstall Qt into a device513 \section1 Step 2: Install Qt into a device 515 514 516 515 To run Qt applications on a device, \c{qt_installer.sis} found … … 524 523 Installer" and follow the instructions. 525 524 526 \oRunning Qt demos525 \section1 Running Qt demos 527 526 528 527 We've included a subset of the Qt demos in this package for you … … 548 547 see \l{The Symbian platform - Introduction to Qt}. 549 548 550 We hope you will enjoy using Qt. 551 552 \endlist 549 \bold{We hope you will enjoy using Qt.} 550 553 551 554 552 */ 555 553 /*! \page install-Symbian.html 556 \title Installing Qt onthe Symbian platform554 \title Installing Qt for the Symbian platform 557 555 \ingroup installation 558 556 \ingroup qtsymbian 559 \brief How to install Qt on the Symbian platform. 560 561 \note Qt for the Symbian platform has some requirements that are given in more detail 557 \brief How to install Qt for the Symbian platform. 558 \previouspage Installation 559 \tableofcontents 560 561 Qt for the Symbian platform has some requirements that are given in more detail 562 562 in the \l{Qt for the Symbian platform Requirements} document. 563 563 564 \note \bold {This document describes how to install and configure Qt for 565 the Symbian platform from scratch. 566 If you are using pre-built binaries, follow the instructions given in the 567 \l{Installing Qt on the Symbian platform from a Binary Package} document.} 568 569 \list 1 570 571 \o Setup the development environment 572 573 Make sure your Symbian development environment is correctly installed and 574 patched as explained in the \l{Qt for the Symbian platform Requirements} document. 575 576 After you have finished the Symbian development environment setup, it is good 577 to verify that environment is functional for example by compiling one 578 of the pure Symbian examples for both emulator and HW. This can be done from 579 command prompt as follows: 580 581 \snippet doc/src/snippets/code/doc_src_installation.qdoc 32 582 583 If all steps pass without errors your Symbian development environment is 584 very likely installed correctly. 585 586 \o Install Qt 587 588 Uncompress the \l{http://qt.nokia.com/downloads}{downloaded} source package into the 589 directory you want Qt installed, e.g. \c{C:\Qt\4.6.3}. 590 591 \note Qt must be installed on the same drive as the Symbian SDK you are 592 using, and the install path must not contain any spaces. 593 594 \o Environment variables 595 596 In order to build and use Qt, the \c PATH environment variable needs 597 to be extended: 598 599 \snippet doc/src/snippets/code/doc_src_installation.qdoc 18 600 601 This is done by adding \c{c:\Qt\4.6.3\bin} to the \c PATH variable. 602 603 On Windows the PATH can be extended by navigating to 604 "Control Panel->System->Advanced->Environment variables". 605 606 In addition, you must configure the environment for use with the Symbian 607 emulator. This is done by locating the Carbide.c++ submenu on the Start 608 menu, and choosing "Configure environment for WINSCW command line". 609 610 If you are planning to use abld (the default build system that comes with the S60 SDK) 611 to build Qt, you will also need to set the following environment variable: 612 613 \snippet doc/src/snippets/code/doc_src_installation.qdoc 33 614 615 This is not necessary for other applications, only when building Qt. 616 617 \o Configure Qt 618 619 To configure Qt for the Symbian platform, do: 620 621 \snippet doc/src/snippets/code/doc_src_installation.qdoc 23 622 to build the tools using MinGW, and the libraries using abld. 623 or 624 \snippet doc/src/snippets/code/doc_src_installation.qdoc 31 625 to build the tools using MinGW, and the libraries using SBSv2. 626 627 SBSv2 (also known as \l{http://developer.symbian.org/wiki/index.php/Introduction_to_RAPTOR} {Raptor}) 628 is a next-generation Symbian build system. SBSv2 is not officially 629 supported by any of the S60 SDKs currently available from Forum Nokia. 630 631 \o Build Qt 632 633 To build Qt for the emulator, type: 634 635 \snippet doc/src/snippets/code/doc_src_installation.qdoc 24 636 637 To build Qt for the device, type: 638 639 \snippet doc/src/snippets/code/doc_src_installation.qdoc 28 640 641 Congratulations, Qt is now ready to use. 642 643 \o Installing Qt libraries on the device 644 645 To run the demo on a real device, you first have to install 646 the Qt libraries on the device: 647 648 \snippet doc/src/snippets/code/doc_src_installation.qdoc 29 649 650 The Qt libraries are built with "All -Tcb" capability, so that 651 they can support all types of application. 652 If you don't have a suitable certificate, it is possible to patch 653 the binaries as follows: 654 655 \list A 656 \o Installing Qt without a certificate 657 658 If you have no certificate, build a self signed Qt: 659 660 \snippet doc/src/snippets/code/doc_src_installation.qdoc 34 661 662 \o Installing Qt with a Symbian developer certificate 663 664 If you have a symbian-signed developer certificate, specify the 665 capabilities you can sign for, for example: 666 667 \snippet doc/src/snippets/code/doc_src_installation.qdoc 35 668 \endlist 669 670 \o Running Qt demos 671 672 We've included a subset of the Qt demos in this package for you 673 to try out. An excellent starting point is the "fluidlauncher" 674 demo. 675 676 Similarly, install fluidlauncher to the device: 677 678 \snippet doc/src/snippets/code/doc_src_installation.qdoc 30 679 680 This will create a self-signed \c fluidlauncher.sis and 681 install it to your device. 682 683 To run the demos on the emulator simply navigate to the directory of the demo 684 you want to see and run: 685 686 \snippet doc/src/snippets/code/doc_src_installation.qdoc 27 687 688 For more information about building and running Qt programs on the 689 Symbian platform, see \l{The Symbian platform - Introduction to Qt}. 690 564 This document describes how to install and configure Qt for 565 the Symbian platform from scratch. If you are using pre-built binaries, follow 566 the instructions given in the \l{Installing Qt for the Symbian platform from a 567 Binary Package} document. 568 569 \section1 Step 1: Set Up the Development Environment 570 571 Make sure your Symbian development environment is correctly installed 572 and patched as explained in the \l{Qt for the Symbian platform Requirements} 573 document. 574 575 After you have finished the Symbian development environment setup, it is 576 good to verify that environment is functional for example by compiling one 577 of the pure Symbian examples for both emulator and HW. This can be done from 578 command prompt as follows: 579 580 \snippet doc/src/snippets/code/doc_src_installation.qdoc 32 581 582 If all steps pass without errors your Symbian development environment is 583 very likely installed correctly. 584 585 \section1 Step 2: Install Qt 586 587 Uncompress the \l{http://qt.nokia.com/downloads}{downloaded} source 588 package into the directory you want Qt installed, e.g. \c{C:\Qt\4.7.2}. 589 590 \note Qt must be installed on the same drive as the Symbian SDK you are 591 using, and the install path must not contain any spaces. 592 593 \section1 Step 3: Set the Environment variables 594 595 In order to build and use Qt, the \c PATH environment variable needs 596 to be extended: 597 598 \snippet doc/src/snippets/code/doc_src_installation.qdoc 18 599 600 This is done by adding \c{c:\Qt\4.7.2\bin} to the \c PATH variable. 601 602 On Windows the\c PATH can be extended by navigating to 603 "Control Panel->System->Advanced->Environment variables". 604 605 In addition, you must configure the environment for use with the Symbian 606 emulator. This is done by locating the Carbide.c++ submenu on the Start 607 menu, and choosing "Configure environment for WINSCW command line". 608 609 If you are planning to use \c abld (the default build system that comes with 610 the S60 SDK) to build Qt, you will also need to set the following 611 environment variable: 612 613 \snippet doc/src/snippets/code/doc_src_installation.qdoc 33 614 615 This is not necessary for other applications, only when building Qt. 616 617 \section1 Step 4: Configure Qt 618 619 To configure Qt for the Symbian platform, do: 620 621 \snippet doc/src/snippets/code/doc_src_installation.qdoc 23 622 (to build the tools using MinGW, and the libraries using abld) 623 624 \bold or 625 626 \snippet doc/src/snippets/code/doc_src_installation.qdoc 31 627 (to build the tools using MinGW, and the libraries using SBSv2) 628 629 SBSv2 (also known as \l{http://developer.symbian.org/wiki/index.php/Introduction_to_RAPTOR} {Raptor}) 630 is a next-generation Symbian build system. SBSv2 is not officially supported 631 by any of the S60 SDKs currently available from Forum Nokia. 632 633 \section1 Step 5: Build Qt 634 635 To build Qt for the emulator, type: 636 637 \snippet doc/src/snippets/code/doc_src_installation.qdoc 24 638 639 To build Qt for the device, type: 640 641 \snippet doc/src/snippets/code/doc_src_installation.qdoc 28 642 643 Congratulations, Qt is now ready to use. 644 645 \section1 Step 7: Installing Qt Libraries on the Device 646 647 To run the demo on a real device, you first have to install 648 the Qt libraries on the device: 649 650 \snippet doc/src/snippets/code/doc_src_installation.qdoc 29 651 652 The Qt libraries are built with "All -Tcb" capability, so that 653 they can support all types of application. 654 If you don't have a suitable certificate, it is possible to patch 655 the binaries as follows: 656 657 If you have no certificate, build a self signed Qt: 658 \snippet doc/src/snippets/code/doc_src_installation.qdoc 34 659 660 If you have a symbian-signed developer certificate, specify the 661 capabilities you can sign for, for example: 662 \snippet doc/src/snippets/code/doc_src_installation.qdoc 35 663 664 \section1 Running Qt demos 665 666 We've included a subset of the Qt demos in this package for you 667 to try out. An excellent starting point is the "fluidlauncher" 668 demo. 669 670 Similarly, install fluidlauncher to the device: 671 672 \snippet doc/src/snippets/code/doc_src_installation.qdoc 30 673 674 This will create a self-signed \c fluidlauncher.sis and 675 install it to your device. 676 677 To run the demos on the emulator simply navigate to the directory of the demo 678 you want to see and run: 679 680 \snippet doc/src/snippets/code/doc_src_installation.qdoc 27 681 682 For more information about building and running Qt programs on the 683 Symbian platform, see \l{The Symbian platform - Introduction to Qt}. 691 684 We hope you will enjoy using Qt. 692 685 686 */ 687 /*! \page install-symbian-linux.html 688 \title Installing Qt for the Symbian platform using Linux (experimental) 689 \ingroup installation 690 \ingroup qtsymbian 691 \brief How to install Qt for the Symbian platform using Linux. 692 \previouspage Installation 693 \tableofcontents 694 695 This document describes how to install and configure Qt for 696 the Symbian platform from scratch, using Linux as the build host. 697 Qt for Symbian binaries can be downloaded directly so development of 698 applications using Qt for Symbian can start right away. 699 700 \section1 Step 1: Setup the Development Environment 701 702 Qt for the Symbian platform has some requirements on the development 703 platform. The Symbian SDK for Linux as well as a cross compiler for the ARM 704 processor used on Symbian devices should be present on the development 705 machine. 706 707 See \l{http://qt.gitorious.org/qt/pages/QtCreatorSymbianLinux} for more details. 708 709 710 \section1 Step 2: Unpack the Archive 711 712 Uncompress the \l{http://qt.nokia.com/downloads}{downloaded} source package into the 713 directory you want Qt installed, e.g. \c{/home/user/qt/4.7.2}. 714 715 716 \section1 Step 3: Set the Environment Variables 717 718 In order to build and use Qt, the \c PATH environment variable needs 719 to be extended to fine Qt tools and also to find the Symbian platform tools: 720 721 First you need to set the \c EPOCROOT environment variable to point to the 722 location of your S60 SDK: 723 724 \snippet doc/src/snippets/code/doc_src_installation.qdoc 36 725 726 Then you can update the PATH variable; 727 728 \snippet doc/src/snippets/code/doc_src_installation.qdoc 37 729 730 731 \section1 Step 4: Configure Qt 732 733 To configure Qt for the Symbian platform, do: 734 735 \snippet doc/src/snippets/code/doc_src_installation.qdoc 38 736 737 to build the libraries using RVCT or 738 739 \snippet doc/src/snippets/code/doc_src_installation.qdoc 39 740 741 to build the libraries using GCCE. 742 743 744 \section1 Step 5: Build Qt 745 746 To build Qt for the device, type: 747 748 \snippet doc/src/snippets/code/doc_src_installation.qdoc 40 749 750 Congratulations, Qt is now ready to use. 751 752 753 \section1 Step 6: Building Qt Packages for the Device 754 755 To run any application or demo on a real device, you need to install it 756 on the device. To do this you first have to create a a package for the 757 device, containing the libraries: 758 759 \bold{Building a Qt package without a certificate} 760 761 If you have no certificate, build a self signed Qt: 762 763 \snippet doc/src/snippets/code/doc_src_installation.qdoc 41 764 765 The Qt libraries are built with "All -Tcb" capability, so that 766 they can support all types of applications. However, these 767 capabilities are automatically lowered if you make a self-signed 768 package. 769 770 \bold{Building a Qt package with a Symbian developer certificate} 771 772 If you have a Symbian-signed developer certificate, specify the 773 capabilities you can sign for, for example: 774 775 \snippet doc/src/snippets/code/doc_src_installation.qdoc 42 776 777 \section2 Installing Qt Packages to the Device. 778 779 It is possible to install packages to a phone in Linux by putting 780 the package on the phone memory card and then installing manually 781 from the phone menu. However, this is tedious and will not work 782 on phones without a memory card, so the method recommended by Qt is 783 to use the App TRK tool. 784 785 \section3 Obtaining the App TRK package. 786 787 Download the package from the following location. 788 789 \list 790 \o \l{http://tools.ext.nokia.com/trk/}{Application TRK}. 791 Choose the correct installation package based on the 792 S60 version of your device 793 (\c{S60_<S60-version>_app_trk_<TRK-version>.sisx}). 693 794 \endlist 694 795 796 This package currently has to be installed by putting the 797 package on the memory card and installing from the phone 798 menu, or using a Windows PC for doing the install. However, 799 the installation only has to be done once. 800 801 \section3 Configuring App TRK on the Phone 802 803 When App TRK is installed, connect the phone to the PC using 804 the USB cable. Select "PCSuite" as connection type. Then run 805 App TRK on the phone, and make sure that the connection type is 806 USB. This can be changed under the \c Settings menu entry. 807 If necessary, choose \c Connect from the menu. 808 809 \section3 Configuring the USB Serial Driver on the Linux System 810 811 On Linux, phone should appear as the \c /dev/ttyUSB1 device, 812 however if you are running an old kernel, you may need to 813 force the USB module to be loaded correctly before the device 814 will appear: 815 816 \snippet doc/src/snippets/code/doc_src_installation.qdoc 43 817 818 Note the identifier on the line where your Symbian device 819 appears. Then execute the following, using the first and 820 second part of the identifier in place of \c XXX, 821 respectively. 822 823 \snippet doc/src/snippets/code/doc_src_installation.qdoc 44 824 825 The \c rmmod step may fail if the module is not already 826 loaded, but that is harmless. 827 828 \section3 Building the runonphone Tool. 829 830 Note that building the \c runonphone tool requires a separate 831 installation of Qt for Linux. If there is a version of Qt 832 installed by your distribution's package mechanism, that that 833 should do fine. Some distributions separate the libraries from 834 the development setup which includes \c qmake. Make sure you 835 have both installed. 836 837 You will also need the \l{libusb} libraries and header files 838 installed. Usually, installing a development package such as 839 \c{libusb-dev} will ensure that you have all the necessary 840 dependencies installed. 841 842 First, make sure that the \c qmake you use is taken from the 843 Linux installation of Qt. The easiest way to make sure of this 844 is to open a new shell and run the following command: 845 846 \snippet doc/src/snippets/code/doc_src_installation.qdoc 45 847 848 \c qmake will tell you where it is installed. 849 850 Copy the \c{%QTDIR%/tools/runonphone} folder to a place outside 851 of the Qt tree. Then go to the folder in a shell and build it: 852 853 \snippet doc/src/snippets/code/doc_src_installation.qdoc 46 854 855 Copy the resulting executable to a folder which is in your 856 \c PATH environment variable. 857 858 \section3 Installing the Built Package onto the Phone 859 860 \note Before starting, please make sure that there is no previously 861 installed version of Qt on the phone. 862 863 Return to the root of the Qt tree configured for Symbian. Then 864 install the Qt libraries by running the following: 865 866 \snippet doc/src/snippets/code/doc_src_installation.qdoc 47 867 868 You may need to supply the path of the serial device file using 869 the \c{-p} option: 870 871 \snippet doc/src/snippets/code/doc_src_installation.qdoc runonphone with device file path 872 873 If the installation fails, please make sure that there is 874 no previously installed version of Qt on the phone. 875 876 Qt requires some dependent packages to be installed on the device, 877 which can be installed using the runonphone tool as well. One is 878 the \c{sqlite3.sis}, which is included in the Qt distribution, while 879 the others are shipped with the Symbian SDK. The required packages 880 can be found from the following locations: 881 882 \snippet doc/src/snippets/code/doc_src_installation.qdoc 50 883 884 It is also possible to install packages onto the device using the 885 \c runonphone build rule that \c qmake automatically generates for 886 each Qt project. Options can be supplied to the \c runonphone tool 887 that is invoked begind the scenes: 888 889 \snippet doc/src/snippets/code/doc_src_installation.qdoc make runonphone with options 890 891 If you are running \c runonphone or invoking the \c runonphone 892 build rule often, it is possible to set the \c QT_RUN_ON_PHONE_OPTIONS 893 environment variable with the options you normally use: 894 895 \snippet doc/src/snippets/code/doc_src_installation.qdoc make runonphone with preset environment variable 896 897 This makes installation of packages onto a device easier and less 898 error-prone. 899 900 901 \section1 Running Qt Demos 902 903 We've included a subset of the Qt demos in this package for you 904 to try out. An excellent starting point is the "fluidlauncher" 905 demo. 906 907 Install and run the demo by using the following commands: 908 909 \snippet doc/src/snippets/code/doc_src_installation.qdoc 48 910 911 The same command can be used for other applications: 912 913 \snippet doc/src/snippets/code/doc_src_installation.qdoc 49 914 915 For more information about building and running Qt programs on the 916 Symbian platform, see \l{The Symbian platform - Introduction to Qt}. 917 918 We hope you will enjoy using Qt. 695 919 */ 920 696 921 /*! 697 922 \page requirements.html … … 740 965 \l{http://www.microsoft.com/downloads/details.aspx?FamilyId=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en}{here} 741 966 to avoid runtime conflicts. 742 743 If you are using a source code package of Qt, you must first install Perl so 967 Additionally, you must use the Check for Updates feature in the Help menu of the Visual Studio 2005 IDE to apply at least the following security updates: KB937061, KB971023, KB971090, KB973673. 968 969 If you are using a source edition of Qt, you must first install Perl so 744 970 that the syncqt script invoked by configure can be executed. You can download 745 this \l{http://www.activestate /downloads/}{here}.971 this \l{http://www.activestate.com/downloads/}{here}. 746 972 747 973 To build Qt with Phonon on Windows, you require: … … 755 981 \endlist 756 982 757 \sa {Known Issues in 4.6.3}983 \sa {Known Issues} 758 984 */ 759 985 … … 765 991 \previouspage General Qt Requirements 766 992 767 \sa {Known Issues in 4.6.3} 993 Qt requires Xcode to be installed on the system. Xcode should be 994 available on the Mac installation CD. 995 996 \sa {Known Issues} 768 997 */ 769 998 … … 904 1133 distribution's package repository to find suitable packages. 905 1134 906 \sa {Known Issues in 4.6.3}1135 \sa {Known Issues} 907 1136 */ 908 1137 … … 958 1187 \l{Windows CE - Working with Custom SDKs}{here}. 959 1188 960 \sa {Known Issues in 4.6.3}1189 \sa {Known Issues} 961 1190 */ 962 1191 … … 968 1197 \previouspage General Qt Requirements 969 1198 970 \sa {Known Issues in 4.6.3}1199 \sa {Known Issues} 971 1200 972 1201 \section1 Building Qt for Embedded Linux with uclibc … … 1018 1247 Qt for the Symbian platform requires the following software installed on your development PC: 1019 1248 \list 1020 \o \l{http://www.forum.nokia.com/ main/resources/tools_and_sdks/carbide_cpp/}{Carbide.c++ v2.0.0 or higher}1249 \o \l{http://www.forum.nokia.com/Library/Tools_and_downloads/Other/Carbide.c++/}{Carbide.c++ v2.3.0 or higher recommended}. 1021 1250 \list 1022 \o \bold{Note:} It may be necessary to update the Carbide compiler .1251 \o \bold{Note:} It may be necessary to update the Carbide compiler depending on Carbide version. 1023 1252 See \l{http://pepper.troll.no/s60prereleases/patches/}{here} for instructions how to check your 1024 1253 compiler version and how to patch it, if needed. … … 1030 1259 compiled using both 5.8.x and 5.10.x versions. 1031 1260 \endlist 1032 \o \l{http://www.forum.nokia.com/ main/resources/tools_and_sdks/S60SDK/}{S60 Platform SDK 3rd Edition FP1 or higher}1261 \o \l{http://www.forum.nokia.com/info/sw.nokia.com/id/ec866fab-4b76-49f6-b5a5-af0631419e9c/S60_All_in_One_SDKs.html}{S60 Platform SDK 3rd Edition FP1 or higher} 1033 1262 \list 1034 1263 \o \bold{Note:} Users of \bold{S60 Platform SDK 3rd Edition FP1} also need special update. The update can be found 1035 1264 \l{http://pepper.troll.no/s60prereleases/patches/}{here}. 1036 1265 \endlist 1037 \o \l{http://www.forum.nokia.com/ main/resources/technologies/openc_cpp/}{Open C/C++ v1.6.0or higher}.1266 \o \l{http://www.forum.nokia.com/info/sw.nokia.com/id/91d89929-fb8c-4d66-bea0-227e42df9053/Open_C_SDK_Plug-In.html}{Open C/C++ v1.7.5 or higher}. 1038 1267 Install this to all Symbian SDKs you plan to use Qt with. 1039 1268 \o Building Qt tools from scratch requires \l{http://www.mingw.org/}{MinGW 3.4.5 or higher}, or another windows compiler. … … 1041 1270 \o \bold{Note:} This is not required if you are using pre-built binary package. 1042 1271 \endlist 1043 \o Building Qt libraries requires \l{http://www.arm.com/products/ DevTools/RVCT.html}{RVCT} version 2.2 (build 686 or later),1272 \o Building Qt libraries requires \l{http://www.arm.com/products/tools/software-development-tools.php}{RVCT} version 2.2 (build 686 or later), 1044 1273 which is not available free of charge. Usage of later versions of RVCT, including the 3.x and 4.x series, is not supported 1045 1274 in this release. 1046 1275 \endlist 1047 1276 1048 Running Qt on real device requires the Open C to be installed on the device. 1049 The Open C installation packages are embedded into \c{qt_installer.sis}, which is included in 1050 Qt for Symbian binary package. If you are building Qt from scratch, you can find the 1051 required packages in the Symbian SDK where you installed Open C/C++: 1277 Running Qt on real device requires the Open C and sqlite3 to be installed on the device. 1278 These installation packages are embedded into \c{qt_installer.sis}, which is included in 1279 Qt for Symbian binary package. 1280 1281 If you are building Qt from scratch, you can find the sqlite3 package from 1282 under your Qt installation: 1283 1284 \list 1285 \o \c{src\s60installs\sqlite3.sis} 1286 \endlist 1287 1288 The Open C packages you can find in the Symbian SDK where you installed Open C/C++: 1052 1289 \list 1053 1290 \o \c{nokia_plugin\openc\s60opencsis\pips_s60_<version>.sis} … … 1068 1305 to get more information about how to setup the development environment. 1069 1306 1070 \sa {Known Issues in 4.6.3}1307 \sa {Known Issues} 1071 1308 */ 1309 1310 /*! 1311 \page configure-options.html 1312 \title Configure options for Qt 1313 \ingroup installation 1314 \brief Brief description of available options building Qt. 1315 1316 This page gives a brief description of the different options 1317 available when building Qt using configure. To build Qt using 1318 default options, just call configure from the command line like 1319 showed below. If you would like to customize your build, please 1320 use the options listed in the following tables. 1321 1322 \c {.\configure.exe} 1323 1324 \section2 Cross platform options: 1325 1326 \table 1327 \header \o Option \o Description \o Note 1328 \row \o \c {-buildkey } <key> \o Build the Qt library and plugins 1329 using the specified \o 1330 \row \o \c {<key>} \o When the library loads plugins, it will only 1331 load those that have a matching <key>. \o 1332 \row \o \c {-release } \o Compile and link Qt with debugging turned off. \o 1333 \row \o \c {-debug } \o Compile and link Qt with debugging turned on. 1334 \o Defualt value. 1335 \row \o \c {-debug-and-release} \o Compile and link two Qt libraries, 1336 with and without debugging turned on. \o This option denotes a default 1337 value and needs to be evaluated. If the evaluation succeeds, the 1338 feature is included. 1339 \row \o \c {-opensource} \o Compile and link the Open-Source Edition 1340 of Qt. \o 1341 \row \o \c {-commercial } \o Compile and link the Commercial Edition 1342 of Qt. \o 1343 \row \o \c {-developer-build} \o Compile and link Qt with Qt developer 1344 options including auto-tests exporting) \o 1345 \row \o \c {-shared} \o Create and use shared Qt libraries. \o Defualt 1346 value. 1347 \row \o \c {-static} \o Create and use static Qt libraries. \o 1348 \row \o \c {-ltcg} \o Use Link Time Code Generation. \o Apply to release 1349 builds only. 1350 \row \o \c {-no-ltcg} \o Do not use Link Time Code Generation. \o Defualt 1351 value. 1352 \row \o \c {-no-fast} \o Configure Qt normally by generating Makefiles for 1353 all project files. \o Defualt value. 1354 \row \o \c {-fast} \o Configure Qt quickly by generating Makefiles only for 1355 library and subdirectory targets. \o All other Makefiles are created as 1356 wrappers which will in turn run qmake. 1357 \row \o \c {-no-exceptions} \o Disable exceptions on platforms that support 1358 it. \o 1359 \row \o \c {-exceptions} \o Enable exceptions on platforms that support it. 1360 \o Defualt value. 1361 \row \o \c {-no-accessibility} \o Do not compile Windows Active 1362 Accessibility support. \o 1363 \row \o \c {-accessibility} \o Compile Windows Active Accessibility 1364 support. \o Defualt value. 1365 \row \o \c {-no-stl} \o Do not compile STL support. \o 1366 \row \o \c {-stl} \o Compile STL support. \o Defualt value. 1367 \row \o \c {-no-sql-<driver>} \o Disable SQL <driver> entirely, by default 1368 none are turned on. \o 1369 \row \o \c {-qt-sql-<driver>} \o Enable a SQL <driver> in the Qt Library. 1370 \o 1371 \row \o \c {-plugin-sql-<driver>} \o Enable SQL <driver> as a plugin to be 1372 linked to at run time. \o Available values for <driver>: mysql, psql, 1373 oci, odbc, tds, db2, sqlite, sqlite2, ibase. Drivers marked with a 1374 '+' during configure have been detected as available on this system. 1375 \row \o \c {-system-sqlite} \o Use sqlite from the operating system. \o 1376 \row \o \c {-no-qt3support} \o Disables the Qt 3 support functionality. \o 1377 \row \o \c {-no-opengl} \o Disables OpenGL functionality \o 1378 \row \o \c {-opengl <api>} \o Enable OpenGL support with specified API 1379 version. \o Available values for <api>: desktop - Enable support for 1380 Desktop OpenGL (Default), es1 - Enable support for OpenGL ES Common 1381 Profile, es2 - Enable support for OpenGL ES 2.0. 1382 \row \o \c {-no-openvg} \o Disables OpenVG functionality \o Defualt value. 1383 \row \o \c {-openvg} \o Enables OpenVG functionality \o Requires EGL 1384 support, typically supplied by an OpenGL or other graphics 1385 implementation. 1386 \row \o \c {-platform <spec> } \o The operating system and compiler you 1387 are building on. \o The default value is %QMAKESPEC%. 1388 \row \o \c {-xplatform <spec> } \o The operating system and compiler you 1389 are cross compiling to. \o See the README file for a list of supported 1390 operating systems and compilers. 1391 \row \o \c {-qtnamespace <namespace>} \o Wraps all Qt library code in 1392 'namespace name {..} \o 1393 \row \o \c {-qtlibinfix <infix>} \o Renames all Qt* libs to Qt*<infix> 1394 \o 1395 \row \o \c {-D <define>} \o Add an explicit define to the preprocessor. 1396 \o 1397 \row \o \c {-I <includepath>} \o Add an explicit include path. \o 1398 \row \o \c {-L <librarypath>} \o Add an explicit library path. \o 1399 \row \o \c {-l <libraryname>} \o Add an explicit library name, residing 1400 in a librarypath. \o 1401 \row \o \c {-graphicssystem <sys>} \o Specify which graphicssystem should 1402 be used. \o Available values for <sys>: * raster - Software rasterizer, 1403 opengl - Using OpenGL acceleration, experimental!, openvg - Using 1404 OpenVG acceleration, experimental! 1405 \row \o \c {-help, -h, -?} \o Display this information. \o 1406 \endtable 1407 1408 \section2 Third Party Libraries: 1409 \table 1410 \header \o Option \o Description \o Note 1411 \row \o \c {-qt-zlib} \o Use the zlib bundled with Qt. \o 1412 \row \o \c {-system-zlib} \o Use zlib from the operating system. 1413 \o See http://www.gzip.org/zlib 1414 \row \o \c {-no-gif} \o Do not compile GIF reading support. 1415 \o This option denotes a default value and needs to be evaluated. 1416 If the evaluation succeeds, the feature is included. 1417 \row \o \c {-qt-gif} \o Compile GIF reading support. \o See also 1418 src/gui/image/qgifhandler_p.h 1419 \row \o \c {-no-libpng} \o Do not compile PNG support. \o 1420 \row \o \c {-qt-libpng} \o Use the libpng bundled with Qt. 1421 \o This option denotes a default value and needs to be evaluated. 1422 If the evaluation succeeds, the feature is included. 1423 \row \o \c {-system-libpng} \o Use libpng from the operating system. 1424 \o See http://www.libpng.org/pub/png 1425 \row \o \c {-no-libmng} \o Do not compile MNG support. \o This option 1426 denotes a default value and needs to be evaluated. If the evaluation 1427 succeeds, the feature is included. 1428 \row \o \c {-qt-libmng} \o Use the libmng bundled with Qt. \o 1429 \row \o \c {-system-libmng} \o Use libmng from the operating system. 1430 \o See See http://www.libmng.com 1431 \row \o \c {-no-libtiff} \o Do not compile TIFF support. \o This option 1432 denotes a default value and needs to be evaluated. If the evaluation 1433 succeeds, the feature is included. 1434 \row \o \c {-qt-libtiff} \o Use the libtiff bundled with Qt. \o 1435 \row \o \c {-system-libtiff} \o Use libtiff from the operating system. 1436 \o See http://www.libtiff.org 1437 \row \o \c {-no-libjpeg} \o Do not compile JPEG support. \o This option 1438 denotes a default value and needs to be evaluated. If the evaluation 1439 succeeds, the feature is included. 1440 \row \o \c {-qt-libjpeg} \o Use the libjpeg bundled with Qt. \o 1441 \row \o \c {-system-libjpeg} \o Use libjpeg from the operating system. 1442 \o See http://www.ijg.org. This option denotes a default value and 1443 needs to be evaluated. If the evaluation succeeds, the feature is 1444 included. 1445 \endtable 1446 1447 \section2 Qt for Windows only: 1448 \table 1449 \header \o Option \o Description \o Note 1450 \row \o \c {-no-dsp} \o Do not generate VC++ .dsp files. \o 1451 \row \o \c {-dsp} \o Generate VC++ .dsp files, only if spec "win32-msvc". 1452 \o Defualt value. 1453 \row \o \c {-no-vcproj} \o Do not generate VC++ .vcproj files. \o 1454 \row \o \c {-vcproj} \o Generate VC++ .vcproj files, only if platform 1455 "win32-msvc.net". \o Defualt value. 1456 \row \o \c {-no-incredibuild-xge} \o Do not add IncrediBuild XGE distribution 1457 commands to custom build steps. \o 1458 \row \o \c {-incredibuild-xge} \o Add IncrediBuild XGE distribution commands 1459 to custom build steps. This will distribute MOC and UIC steps, and other 1460 custom buildsteps which are added to the INCREDIBUILD_XGE variable. 1461 \o The IncrediBuild distribution commands are only added to Visual Studio 1462 projects. This option denotes a default value and needs to be evaluated. 1463 If the evaluation succeeds, the feature is included. 1464 \row \o \c {-no-plugin-manifests} \o Do not embed manifests in plugins. \o 1465 \row \o \c {-plugin-manifests} \o Embed manifests in plugins. 1466 \o Defualt value. 1467 \row \o \c {-no-qmake} \o Do not compile qmake. \o 1468 \row \o \c {-qmake} \o Compile qmake. \o Defualt value 1469 \row \o \c {-dont-process} \o Do not generate Makefiles/Project files. This 1470 will override -no-fast if specified. \o 1471 \row \o \c {-process} \o Generate Makefiles/Project files. \o Defualt value. 1472 \row \o \c {-no-rtti} \o Do not compile runtime type information. \o 1473 \row \o \c {-rtti} \o Compile runtime type information. \o Defualt value. 1474 \row \o \c {-no-mmx} \o Do not compile with use of MMX instructions \o 1475 \row \o \c {-mmx} \o Compile with use of MMX instructions \o This option 1476 denotes a default value and needs to be evaluated. If the evaluation 1477 succeeds, the feature is included. 1478 \row \o \c {-no-3dnow} \o Do not compile with use of 3DNOW instructions \o 1479 \row \o \c {-3dnow} \o Compile with use of 3DNOW instructions \o This 1480 option denotes a default value and needs to be evaluated. If the 1481 evaluation succeeds, the feature is included. 1482 \row \o \c {-no-sse} \o Do not compile with use of SSE instructions \o 1483 \row \o \c {-sse} \o Compile with use of SSE instructions \o This option 1484 denotes a default value and needs to be evaluated. If the evaluation 1485 succeeds, the feature is included. 1486 \row \o \c {-no-sse2} \o Do not compile with use of SSE2 instructions \o 1487 \row \o \c {-sse2} \o Compile with use of SSE2 instructions \o This option 1488 denotes a default value and needs to be evaluated. If the evaluation 1489 succeeds, the feature is included. 1490 \row \o \c {-no-openssl} \o Do not compile in OpenSSL support \o 1491 \row \o \c {-openssl} \o Compile in run-time OpenSSL support \o This option 1492 denotes a default value and needs to be evaluated. If the evaluation 1493 succeeds, the feature is included. 1494 \row \o \c {-openssl-linked} \o Compile in linked OpenSSL support \o 1495 \row \o \c {-no-dbus} \o Do not compile in D-Bus support \o 1496 \row \o \c {-dbus} \o Compile in D-Bus support and load libdbus-1 dynamically. 1497 \o This option denotes a default value and needs to be evaluated. 1498 If the evaluation succeeds, the feature is included. 1499 \row \o \c {-dbus-linked} \o Compile in D-Bus support and link to 1500 libdbus-1 \o 1501 \row \o \c {-no-phonon} \o Do not compile in the Phonon module \o 1502 \row \o \c {-phonon} \o Compile the Phonon module. \o Phonon is built if a 1503 decent C++ compiler is used. This option denotes a default value and needs 1504 to be evaluated. If the evaluation succeeds, the feature is included. 1505 \row \o \c {-no-phonon-backend} \o Do not compile the platform-specific 1506 Phonon backend-plugin \o 1507 \row \o \c {-phonon-backend} \o Compile in the platform-specific Phonon 1508 backend-plugin \o Defualt value. 1509 \row \o \c {-no-multimedia} \o Do not compile the multimedia module \o 1510 \row \o \c {-multimedia} \o Compile in multimedia module \o Defualt value. 1511 \row \o \c {-no-audio-backend} \o Do not compile in the platform audio 1512 backend into QtMultimedia \o 1513 \row \o \c {-audio-backend} \o Compile in the platform audio backend into 1514 QtMultimedia \o This option denotes a default value and needs to be 1515 evaluated. If the evaluation succeeds, the feature is included. 1516 \row \o \c {-no-webkit} \o Do not compile in the WebKit module \o 1517 \row \o \c {-webkit} \o Compile in the WebKit module \o WebKit is built 1518 if a decent C++ compiler is used. This option denotes a default value 1519 and needs to be evaluated. If the evaluation succeeds, the feature is 1520 included. 1521 \row \o \c {-webkit-debug} \o Compile in the WebKit module with debug 1522 symbols. \o 1523 \row \o \c {-no-script} \o Do not build the QtScript module. \o 1524 \row \o \c {-script} \o Build the QtScript module. \o This option 1525 denotes a default value and needs to be evaluated. If the evaluation 1526 succeeds, the feature is included. 1527 \row \o \c {-no-scripttools} \o Do not build the QtScriptTools module. \o 1528 \row \o \c {-scripttools} \o Build the QtScriptTools module. \o This 1529 option denotes a default value and needs to be evaluated. If the 1530 evaluation succeeds, the feature is included. 1531 \row \o \c {-no-declarative} \o Do not build the declarative module \o 1532 \row \o \c {-declarative} \o Build the declarative module \o This option 1533 denotes a default value and needs to be evaluated. If the evaluation 1534 succeeds, the feature is included. 1535 \row \o \c {-no-declarative-debug} \o Do not build the declarative debugging 1536 support \o 1537 \row \o \c {-declarative-debug} \o Build the declarative debugging support 1538 \o Defualt value. 1539 \row \o \c {-arch <arch>} \o Specify an architecture. \o Available values for 1540 <arch>: * windows, windowsce, symbian, boundschecker, generic. 1541 \row \o \c {-no-style-<style>} \o Disable <style> entirely. \o 1542 \row \o \c {-qt-style-<style>} \o Enable <style> in the Qt Library. 1543 \o Available styles: * windows, + windowsxp, + windowsvista, 1544 * plastique, * cleanlooks, * motif, * cde, windowsce, windowsmobile, 1545 s60 1546 \row \o \c {-no-native-gestures} \o Do not use native gestures on Windows 7. 1547 \o 1548 \row \o \c {-native-gestures} \o Use native gestures on Windows 7. 1549 \o Defualt value. 1550 \row \o \c {-no-mp} \o Do not use multiple processors for compiling with MSVC 1551 \o Defualt value. 1552 \row \o \c {-mp} \o Use multiple processors for compiling with MSVC (-MP) \o 1553 \row \o \c {-loadconfig <config>} \o Run configure with the parameters from file 1554 configure_<config>.cache. \o 1555 \row \o \c {-saveconfig <config>} \o Run configure and save the parameters in 1556 file configure_<config>.cache. \o 1557 \row \o \c {-redo} \o Run configure with the same parameters as last time. \o 1558 \endtable 1559 1560 \section2 Qt for Windows CE only: 1561 \table 1562 \header \o Option \o Description \o Note 1563 \row \o \c {-no-iwmmxt} \o Do not compile with use of IWMMXT instructions \o 1564 \row \o \c {-iwmmxt} \o Do compile with use of IWMMXT instructions. \o This is 1565 for Qt for Windows CE on Arm only. This option denotes a default value and 1566 needs to be evaluated. If the evaluation succeeds, the feature is included. 1567 \row \o \c {-no-crt} \o Do not add the C runtime to default deployment rules. 1568 \o Defualt value. 1569 \row \o \c {-qt-crt} \o Qt identifies C runtime during project generation \o 1570 \row \o \c {-crt <path>} \o Specify path to C runtime used for project 1571 generation. \o 1572 \row \o \c {-no-cetest} \o Do not compile Windows CE remote test application \o 1573 \row \o \c {-cetest} \o Compile Windows CE remote test application \o This 1574 option denotes a default value and needs to be evaluated. If the evaluation 1575 succeeds, the feature is included. 1576 \row \o \c {-signature <file>} \o Use file for signing the target project \o 1577 \row \o \c {-phonon-wince-ds9} \o Enable Phonon Direct Show 9 backend for 1578 Windows CE \o Defualt value 1579 \endtable 1580 1581 \section2 Qt for Symbian OS only: 1582 \table 1583 \header \o Option \o Description \o Note 1584 \row \o \c {-no-freetype} \o Do not compile in Freetype2 support. 1585 \o Defualt value. 1586 \row \o \c {-qt-freetype} \o Use the libfreetype bundled with Qt. \o 1587 \row \o \c {-fpu <flags>} \o VFP type on ARM, supported options: 1588 softvfp(default) |vfpv2 | softvfp+vfpv2 \o 1589 \row \o \c {-no-s60} \o Do not compile in S60 support. \o 1590 \row \o \c {-s60} \o Compile with support for the S60 UI Framework 1591 \o Defualt value. 1592 \row \o \c {-no-usedeffiles} \o Disable the usage of DEF files. \o 1593 \row \o \c {-usedeffiles} \o Enable the usage of DEF files. \o 1594 \endtable 1595 */ -
trunk/doc/src/getting-started/known-issues.qdoc
r769 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 42 28 /*! 43 29 \page known-issues.html 44 \title Known Issues in 4.6.330 \title Known Issues 45 31 \ingroup platform-specific 46 \brief A summary of known issues in Qt 4.6.3at the time of release.32 \brief Links to online resources stating known issues in this Qt version at the time of release. 47 33 48 An up-to-date list of known issues with Qt 4.6.3 can be found via the 49 \l{http://bugreports.qt.nokia.com/}{Qt Bug Tracker}. 50 51 For a list list of known bugs in Qt 4.6.3, see the \l{Task Tracker} 52 on the Qt website. 53 54 An overview of known issues may also be found at: 55 \l{http://qt.gitorious.org/qt/pages/QtKnownIssues} 34 \list 35 \o An up-to-date list of known issues can be found at \l{http://bugreports.qt.nokia.com/}{Qt Bug Tracker}. 36 \o For a list list of known bugs, see the \l{Task Tracker} at the Qt website. 37 \o An overview of known issues may also be found at: \l{http://qt.gitorious.org/qt/pages/QtKnownIssues} 56 38 {Known Issues Wiki}. 57 58 \section1 Installation Issues59 60 \section2 Installing the Source Package on Unix systems61 62 \list63 64 \o If you download a Zip source package, you will need to convert65 Windows-style line endings (CR/LF) to Unix-style line-endings (LF) when66 you uncompress the package. To do this, give the "-a" option when you67 run the "unzip' command.68 69 \o If you fail to supply the "-a" option when unzipping the package, you70 will see the following error message when you attempt to execute the71 configure command:72 "bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory"73 74 \endlist75 76 \section2 Installing on Mac OS X 10.6 "Snow Leopard"77 78 \list79 80 \o Performing a new install of the Qt 4.6 beta on Snow Leopard81 triggers a bug in the installer that causes the install to fail.82 Updating an existing Qt installation works fine.83 84 \o There are two workarounds, either disable spotlight for the target85 drive during the install, or do a custom install where you deselect86 documentation and examples. Run the installer again as a full87 install to get the documentation and examples installed.88 89 \endlist90 91 \section1 Issues with Third Party Software92 93 \section2 X1194 95 \list96 \o There is a bug in the 169.xx NVIDIA drivers on certain GeForce 8 series97 cards that is triggered by the OpenGL paint engine when using QPainter98 on a QGLWidget to draw paths and polygons. Some other painting99 operations that end up in the path fallback are affected as well. The100 bug causes the whole X server to repeatedly hang for several seconds at101 a time.102 \o There is an issue with NVIDIA's 9xxx driver series on X11 that causes a103 crash in cases where there are several \l{QGLContext}s and the extended104 composition modes are used (the composition modes between and including105 QPainter::CompositionMode_Multiply and106 QPainter::CompositionMode_Exclusion). This affects the composition mode107 demo in Qt 4.5, for example. The crash does not occur in newer versions108 of the drivers.109 \endlist110 111 \section2 Windows112 113 \list114 115 \o When using version 6.14.11.6921 of the NVIDIA drivers for the GeForce116 6600 GT under Windows XP, Qt applications which use drag and drop will117 display reduced size drag and drop icons when run alongside118 applications that use OpenGL. This problem can be worked around by119 reducing the level of graphics acceleration provided by the driver, or120 by disabling hardware acceleration completely.121 122 \o With NVIDIA GeForce 7950 GT (driver version 6.14.11.7824), a fullscreen123 QGLWidget flickers when child widgets are shown/hidden. The workaround124 for this is to use \l{QWidget::}{setGeometry()} with a width/height 1125 pixel bigger than your geometry and call \l{QWidget::}{show()}.126 127 \o A bug in the Firebird database can cause an application to crash when128 \c{fbembed.dll} is unloaded. The bug is fixed in version 2.5.129 130 \o On Windows 7, resizing windows is slower than on Vista/Xp. This is because131 the gesture initialization process (required for native gesture support)132 currently calls winId() on widgets, which causes whole widget hierarchies133 to use native window handles. This slows down resizing.134 135 \o Compile errors with Intel C++ Compiler.\br136 There seems to be a bug in the Intel compiler with respect to137 over-agressive inlining of code.138 The problem will manifest itself during the link phase of QtGui where139 it fails with the error that it cannot find QObjectData::~QObjectData().140 See \l{http://bugreports.qt.nokia.com/browse/QTBUG-5145} for updates on this141 bug.142 Also, due to some bugs in WebKit, the QtScript and QtWebKit modules143 will not compile.144 See \l{http://bugreports.qt.nokia.com/browse/QTBUG-6297} for a145 workaround for QtScript.146 147 \endlist148 149 \section2 Mac OS X150 151 \list152 153 \o If a sheet is opened for a given window, clicking the title bar of that154 window will cause it to flash. This behavior has been reported to Apple155 (bug number 5827676).156 157 \endlist158 159 \section2 Symbian160 161 \list162 \o Check known issues for Symbian at163 \l{http://qt.gitorious.org/qt/pages/QtKnownIssues} {Known Issues Wiki}.164 39 \endlist 165 40 */ -
trunk/doc/src/getting-started/tutorials.qdoc
r651 r846 1 1 /**************************************************************************** 2 2 ** 3 ** Copyright (C) 201 0Nokia Corporation and/or its subsidiary(-ies).3 ** Copyright (C) 2011 Nokia Corporation and/or its subsidiary(-ies). 4 4 ** All rights reserved. 5 5 ** Contact: Nokia Corporation (qt-info@nokia.com) … … 7 7 ** This file is part of the documentation of the Qt Toolkit. 8 8 ** 9 ** $QT_BEGIN_LICENSE: LGPL$9 ** $QT_BEGIN_LICENSE:FDL$ 10 10 ** Commercial Usage 11 11 ** Licensees holding valid Qt Commercial licenses may use this file in 12 12 ** accordance with the Qt Commercial License Agreement provided with the 13 ** Software or, alternatively, in accordance with the terms contained in 14 ** awritten agreement between you and Nokia.13 ** Software or, alternatively, in accordance with the terms contained in a 14 ** written agreement between you and Nokia. 15 15 ** 16 ** GNU Lesser General Public License Usage 17 ** Alternatively, this file may be used under the terms of the GNU Lesser 18 ** General Public License version 2.1 as published by the Free Software 19 ** Foundation and appearing in the file LICENSE.LGPL included in the 20 ** packaging of this file. Please review the following information to 21 ** ensure the GNU Lesser General Public License version 2.1 requirements 22 ** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html. 23 ** 24 ** In addition, as a special exception, Nokia gives you certain additional 25 ** rights. These rights are described in the Nokia Qt LGPL Exception 26 ** version 1.1, included in the file LGPL_EXCEPTION.txt in this package. 27 ** 28 ** GNU General Public License Usage 29 ** Alternatively, this file may be used under the terms of the GNU 30 ** General Public License version 3.0 as published by the Free Software 31 ** Foundation and appearing in the file LICENSE.GPL included in the 32 ** packaging of this file. Please review the following information to 33 ** ensure the GNU General Public License version 3.0 requirements will be 34 ** met: http://www.gnu.org/copyleft/gpl.html. 16 ** GNU Free Documentation License 17 ** Alternatively, this file may be used under the terms of the GNU Free 18 ** Documentation License version 1.3 as published by the Free Software 19 ** Foundation and appearing in the file included in the packaging of this 20 ** file. 35 21 ** 36 22 ** If you have questions regarding the use of this file, please contact … … 86 72 tools provided for developers, translators and release managers. 87 73 74 75 \row 76 \o{2,1} \l{modelview.html}{\bold{ModelView}} 77 \o{2,1} 78 79 \row 80 \o \image treeview_sml.png ModelView 81 \o This tutorial gives an introduction to ModelView programming using the Qt cross-platform framework 82 83 \o 84 \o 85 86 \row 87 \o{2,1} \l{QML Tutorial}{\bold QML Tutorial} 88 \o{2,1} \l{QML Advanced Tutorial}{\bold SameGame} 89 \row 90 \o{2,1} 91 This tutorial provides a very basic introduction to QML. 92 \o \image qml-samegame-demo-small.png Samegame 93 \o 94 This tutorial walks through creating a complete application with QML, 95 in this case a simple game. It is recommended that you complete the basic QML 96 tutorial first. 97 88 98 \row 89 99 \o{2,1} \l{QTestLib Tutorial}{\bold QTestLib}
Note:
See TracChangeset
for help on using the changeset viewer.