POPPUR爱换

 找回密码
 注册

QQ登录

只需一步,快速开始

手机号码,快捷登录

搜索
查看: 1147|回复: 2
打印 上一主题 下一主题

ICC不支持.net?

[复制链接]
跳转到指定楼层
1#
发表于 2007-12-4 01:48 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
下了个ICC 10.1 readme 里如此写道 。。。。
Known Issues

    * Limitations on Microsoft Visual C++ language support
      There are a number of new features introduced by Visual C++ that are not support by this version of Intel C++ Compiler for Windows. Please read the User's Guide for additional information.
          o Attributed code is not supported
          o Event handling (new keywords) is not supported
             o Managed extensions for C++ is not supported
* Limitations on project types
          o The Intel C++ compiler only supports native (non-managed) project types such as "Win32 Console Project", "Win32 Application", etc. Project types with .NET attributes such as the ones below cannot be converted to an Intel C++ project:
                + Empty Project (.NET)
                + Class Library (.NET)
                + Console Application (.NET)
                + Windows Control Library (.NET)
                + Windows Forms Application (.NET)
                + Windows Service (.NET)

    * Limitations on integration with Visual Studio 2005
          o Link error for MFC-based applications
            When building non-console applications with MFC support, the following link error may occur:
            error LNK2019: unresolved external symbol _WinMain@16 referenced in function ___tmainCRTStartup

            It happens for projects with the following project properties settings:
                + General/Configuration Type = "Application (.exe)"
                + General/Use Of MFC = "Use MFC in a Static Library" or "Use MFC in a Shared DLL"
                + Linker/System/SubSystem = Any value which is different from "Console (/SUBSYSTEM:CONSOLE)"

            The workaround is:
            Set the Project Property Linker/Advanced/Entry Point = wWinMainCRTStartup
          o Problem with building an ATL DLL project
            When compiling an ATL DLL project with Intel C++ Compiler within Visual Studio 2005, you may see the following error at the end when registering the DLL.
            error PRJ0019: A tool returned an error code from "Performing registration"

            The work around is to add the following commands into the "Post Build Event" in the Project Property/Build Events/Post-Build Event:
                + mt /nologo /manifest $(TargetPath).manifest /outputresource:"$(TargetPath);#2"
                + C:/Winnt/System32/regsvr32 /s /c "$(TargetPath)"
    * Limitation with the Intel Debugger (IDB)
          o The Intel Debugger is not supported on Windows systems with the Standard Edition of Visual C++ .NET (2002 or 2003) installed.
    * There will be an increase in compile time when /Zi is used together with inlining. Inlining can happen if the user specifies /Qipo, /Qip or compiles a C++/C99 program at option levels /O1 or above. This is due to the generation of debug information. For many applications, this combination of compiler options will not increase compile time or compile-time memory use.
2#
发表于 2007-12-4 01:59 | 只看该作者
原帖由 boris_lee 于 2007-12-4 01:48 发表
下了个ICC 10.1 readme 里如此写道 。。。。

ICC只支持生成Native代码,不支持生成CLI中间语言代码。
回复 支持 反对

使用道具 举报

3#
发表于 2007-12-4 02:48 | 只看该作者
:unsure: :unsure:
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

广告投放或合作|网站地图|处罚通告|

GMT+8, 2025-8-30 12:53

Powered by Discuz! X3.4

© 2001-2017 POPPUR.

快速回复 返回顶部 返回列表