Intel® C++ Compiler for MeeGo*, Windows*-cross Release Notes
Installation Guide and Release Notes
20 May 2011
1 Introduction
The Intel AppUp™ SDK Suite for MeeGo* provides a compiler, debugger and high performance libraries for developing 32-bit applications for the MeeGo* operating system.
The Intel AppUp™ SDK Suite for MeeGo* integrates into Qt Creator*.
This document provides system requirements, installation instructions, issues and limitations, and legal information.
1.1 Product Contents
Intel AppUp™ SDK Suite for MeeGo* - Intel® C++ Compiler for MeeGo*, Windows* hosted cross compiler for MeeGo* target includes the following components:
|
Component |
Version |
|
Intel® C++ Compiler |
12.0 |
|
Intel® Integrated Performance Primitives |
7.0 |
|
Intel® Threading Building Blocks |
3.0 |
1.1.1 Intel® Integrated Performance Primitives Cryptography Libraries
Due to United States export laws, the cryptography component of the Intel® IPP library is distributed separately and requires a special registration process. To obtain the cryptography component follow the instructions contained in this article: Obtaining the Intel® IPP Library Cryptography Components for the Intel AppUp™ SDK Suite for MeeGo* available at http://appdeveloper.intel.com/en-us/article/obtaining-ipp-cryptography-for-intel-appup-sdk-for-meego.
1.2 System Requirements
For an explanation of architecture names, see
http://software.intel.com/en-us/articles/intel-architecture-platform-terminology/
Requirements to develop applications
- A PC based on an IA-32 or Intel® 64 architecture processor supporting the Intel® Streaming SIMD Extensions 3 (Intel® SSE3) instructions (Intel® Core™2 Duo processor or later, Intel® Atom™ processor, or compatible non-Intel processor)
- 1GB of RAM (2GB recommended)
- 300MB free disk space for all features
- Windows 7* Professional or Windows XP* SP3 for 32-bit only
- MeeGo* SDK v1.2
Requirements to run applications for tablets
- Intel® Atom™ N330 processor or later (Intel® Atom™ N450 processor recommended)
- MeeGo* Developer Preview for tablets
Requirements to run applications for netbooks
- Intel® Atom™ N270 processor or later (Intel® Atom™ N450 processor recommended)
- MeeGo* v1.2 for netbooks
1.3 Technical Support, Documentation and Samples
For information about how to find Technical Support, product documentation and samples, please visit http://appdeveloper.intel.com/en-us/article/intel-appup-sdk-suite-meego-support-articles.
|
Optimization Notice |
|
Intel® compilers, associated libraries and associated development tools may include or utilize options that optimize for instruction sets that are available in both Intel® and non-Intel microprocessors (for example SIMD instruction sets), but do not optimize equally for non-Intel microprocessors. In addition, certain compiler options for Intel compilers, including some that are not specific to Intel micro-architecture, are reserved for Intel microprocessors. For a detailed description of Intel compiler options, including the instruction sets and specific microprocessors they implicate, please refer to the “Intel® Compiler User and Reference Guides” under “Compiler Options." Many library routines that are part of Intel® compiler products are more highly optimized for Intel microprocessors than for other microprocessors. While the compilers and libraries in Intel® compiler products offer optimizations for both Intel and Intel-compatible microprocessors, depending on the options you select, your code and other factors, you likely will get extra performance on Intel microprocessors. Intel® compilers, associated libraries and associated development tools may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include Intel® Streaming SIMD Extensions 2 (Intel® SSE2), Intel® Streaming SIMD Extensions 3 (Intel® SSE3), and Supplemental Streaming SIMD Extensions 3 (Intel® SSSE3) instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. While Intel believes our compilers and libraries are excellent choices to assist in obtaining the best performance on Intel® and non-Intel microprocessors, Intel recommends that you evaluate other compilers and libraries to determine which best meet your requirements. We hope to win your business by striving to offer the best performance of any compiler or library; please let us know if you find we do not. Notice revision #20101101 |
2 Installation Notes
To begin installation, double-click on the executable file (.EXE) to begin installation. Follow the prompts in the dialogs to complete installation.
2.1 Default Installation Folders
The default top-level installation folder for this product is:
- C:\AppUp-MeeGo-Tools\ICC-MeeGo-host-12.0.U.NNN
Where U is the update number and NNN is the package number. This product installs into an arrangement of folders shown in the diagram below. Not all folders will be present in a given installation.
- C:\AppUp-MeeGo-Tools\ICC-MeeGo-host-12.0.U.NNN
- bin
- ia32
- compiler
- include
- ia32
- lib
- ia32
- crt
- locale
- ia32
- perf_headers
- c++
- substitute_headers
- include
- Documentation
- en_US
- ipp
- bin
- include
- lib
- ia32
- tools
- ia32
- staticlib
- ia32
- qt_support
- linux-icc-v12
- tbb
- bin
- ia32
- build
- vsproject
- include
- tbb
- compat
- machine
- tbb
- lib
- ia32
- bin
- bin
2.2 Changing, Updating and Removing the Product
Use the Windows* Control Panel “Add or Remove Products” applet to change which product components are installed or to remove the product.
2.3 Known Issues and Limitations
- Installation may corrupt your PATH system environment variable if the current environment variable size is close to the maximum size allowed for all environment variables. Clean up your PATH environment variable and any other large environment variable settings before installation to ensure this does not occur.
- If you have both versions 1.1 and 1.2 of the MeeGo* SDK installed, the Intel® C++ Compiler installation will require removal of version 1.1 of the SDK before it can be successfully installed.
3 Intel® C++ Compiler
This section summarizes changes, new features and late-breaking news about the Intel C++ Compiler.
3.1 Using the compiler with Nokia* Qt* Simulator
If you are interested in debugging your Qt* API application natively on Windows* using the Qt* Simulator, please refer to the article, “Running an App in Qt* Simulator Using Intel® C++ Compiler for MeeGo*”.
3.2 Compiler Options Supported in Intel® C++ Composer XE 2011 not in this release
For users of the Intel® C++ Compiler in other products, the following compiler options supported in those products are not available in this release:
- -ax
- -cilk-serialize
- -diag-enable sc
- -diag-sc-dir
- -[no-]intel-extensions
- -m64
- -march
- -mcmodel
- -mcpu
- -mkl
- -mtune
- -openmp
- -par*
- -auto-ilp32
- -tcollect
- -x (only valid for -xSSE3_ATOM)
3.3 Known Issues
3.3.1 -ipp Results in Library not found at Link
You may get a library not found error at link time when using -ipp. Use of this option is not recommended. See http://appdeveloper.intel.com/en-us/article/using-intel-ipp-with-intel-appup-sdk-for-meego
Please see the Intel AppUp™ SDK Suite for MeeGo* Known Issues page for more updated information.
4 Intel® Integrated Performance Primitives
You can read the release notes for the Intel® Integrated Performance Primitives (including information on how to obtain the cryptography libraries) at http://appdeveloper.intel.com/en-us/article/intel-ipp-7.0-release-notes-for-intel-appup-sdk-for-meego.
5 Intel® Threading Building Blocks
You can read the release notes for the Intel® Threading Building Blocks at http://appdeveloper.intel.com/en-us/article/intel-threading-building-blocks-meego-release-notes.
6 Disclaimer and Legal Information
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different processor families. Go to:
http://www.intel.com/products/processor_number/
Software and workloads used in performance tests may have been optimized for performance only on Intel microprocessors. Performance tests, such as SYSmark and MobileMark, are measured using specific computer systems, components, software, operations and functions. Any change to any of those factors may cause the results to vary. You should consult other information and performance tests to assist you in fully evaluating your contemplated purchases, including the performance of that product when combined with other products. For more information go to http://www.intel.com/performance
Intel AppUp, Intel Atom, Intel Core, and Xeon are trademarks of Intel Corporation in the U.S. and other countries.
* Other names and brands may be claimed as the property of others.
Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.
Copyright (C) 2011, Intel Corporation. All rights reserved.
Comments
Hello,
In reply to:
The Intel C++ compiler does not replace the IDE or the SDK, it simply replaces the GCC compiler for use within the Qt IDE and MeeGo SDK. Everything else works the same, whether you are talking about debugging or generating an RPM file. In other words, if you choose to use the Intel C++ compiler with your MeeGo SDK it means that your code will be compiled using the Intel compiler rather than the GCC compiler.
The Qt IDE has no relationship to Microsoft Visual Studio, however, there is an option to create Qt applications that can be built for Windows, in which case there is some integration with Visual Studio -- but that has nothing to do with MeeGo. The MeeGo SDK uses Qt as an IDE and cross-development platform to generate MeeGo applications. When you use the MeeGo SDK on a Windows machine you are creating applications that will run on a MeeGo machine, which is a Linux machine with the MeeGo API running on top.
Hope that helps,
Paul
Hi, I am assuming the Intel C++ Compiler replaces the QT IDE for compiling code for MeeGo. My question is how does the new compiler produce the RPM distributable file, and does the compiler allow remote debugging on target MeeGo devices? I also noticed there was no requirement for Visual Studio to be installed, so is the IDE part of the Compiler download, or do we still use the QT IDE for coding? My interest stems from finding an alternative build environment for producing MeeGo RPMs (in the style of Visual Studio) rather than QT, and using the optimised Intel C++ Compiler and associated tools to improve overall performance on the resulting app.