Menu
▾
▴
[Pfspd-users@sf.net] mtk and cpfspd release
|
From: Bram R. <bra...@nx...> - 2009-11-19 15:14:31
|
Dear all, Today I released mtk and cpfspd. Within NXP, the software is installed at the standard location and the 'latest' links are updated. The release kits can also be downloaded from https://sourceforge.net/projects/pfspd/files/ With this release, we support 64 bits code on windows and Linux. The release kit contains the platforms: win32, win64, cygwin, Linux, Linux64. Check the MTK Readme file how to install various MSVC compiler versions in the cygwin environment. --------------------------- MTK release 5.4.0 --------------------------- Highlights Support for 64 bit platforms on windows and Linux. Bug fixes - None Functionality - A new build option ARCH is added. Default: ARCH=32, which is compatible with all previous behaviour. It is available for a limited number of compilers: + COMP=gcc ARCH=64: generation of 64 bits code as platform "Linux64" + COMP=msvc ARCH=64: generation of 64 bits code as platform "win64" MTK help text and dump output is adapted accordingly. Note that the souce code must be suitable for 64 bits compilation in order to behave "polite" - see section "64 bit code generation" above. Further, 64 bits code for msvc is implemented and tested on the following environments: + Microsoft® Windows® Software Development Kit Update for Windows Vista + Microsoft Visual Studio 2005 + Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 + Microsoft Visual Studio 2008 - The msvc compiler uses an environment variable LIB containing a list of standard library directories. For 64 bit compilation, MTK requires an environment variable LIB64 containing equivalent list for 64 bit library directories. This must be defined by the user. - Buffer length of string generated by parse_options is increased from 1024 to 2048. - The 'inline' keyword is supported by the gcc and msvc C compilers. This is added with the C99 standard. On msvc, this is implemented by substituting "inline" for "__inline". The restrict keyword is still removed. - For MS visual studio version 9.0, the variable RCPATH is not used anymore. Previously, this was defined in the Make.env file. This is substituted by the variable MSVCRC defined in the cygwin.bat file now. Motivation: this is PC installation dependent, and therefore must reside on the system, not the Make.env. Miscellaneous - Copyright date updated. - Code of parse_options is adapted for gcc version 4.x.x, which is more accurate in handling fixed text strings as "const char *". - Parse_options adapted to handle 64 bit compilation on windows and linux platforms. - New section "64 bit code generation" added to the Readme.txt file. - New section "Using Microsoft compilers on cygwin" added in Readme.txt. - MS visual studio version ".NET 2003" is now marked as version 7.1 (was 7) So internal variable MSVC_VERSION now has value "MSVC7.1", not "MSVC7". Also the version test is adapted to distinguish it from the ".NET 2002" version, which is 7.0 (which is not supported). ---------------------------------- CPFSPD release 1.12.1 ---------------------------------- Highlights Added support for 64 bits code generation on windows and Linux platforms as win64 and Linux64 targets. Bug fixes - None Functionality - None Miscellaneous - Copyright date updated. - Upgrade of mtk and parse_options to support 64 bit code generation. Now we support also the win64 and Linux64 platforms. - Some code modifications in cpfspd_fio.c, test and speed programs to handle 64 bit code generation. Tot ziens / Kind regards, Bram -- Bram Riemens Senior Principal, Corporate I&T / Research NXP Semiconductors High Tech Campus 32 (floor 1, office 138), 5656 AE Eindhoven, The Netherlands Tel: +31 40 27 25910; Fax: +31 40 27 28504 Email: bra...@nx... The information contained in this message is confidential and may be legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. Unless otherwise recorded in a written agreement, all sales transactions by NXP Semiconductors are subject to our general terms and conditions of commercial sale. These are published at www.nxp.com/profile/terms/index.html<http://www.nxp.com/profile/terms/index.html> |
