<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated on Wed, 23 May 2012 00:50:33 -0700 -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <atom:link href="http://software.intel.com/en-us/articles/cross-compilation-using-intel-c-compiler-for-linux/feed/" rel="self" type="application/rss+xml" />
    <title>Intel Software Network Comments Feed</title>
    <link>http://software.intel.com/en-us/articles/cross-compilation-using-intel-c-compiler-for-linux</link>
    <description></description>
    <language>en-us</language>
    <item>
      <title>By Florent</title>
      <description><![CDATA[ IMO The resolution does not answer the question properly.
We have the same problem building a library.We use g++ -arch x86_64 -arch i386 for the files of this library, and the intel compiler for specific files of the library.
I noticed that /opt/intel/Compiler/11.1/084/ia32/icc produces i386 object files, and that /opt/intel/Compiler/11.1/084/intel64/icc produces x86_64 object files.

My question is: is there a simple way to use the intel compiler likes g++, meaning with a single call producing a universal binary (i386 x86_64) object file ?

The intel compiler documentation only mentions creating the universal binary by using lipo which is not satisfactory.
 ]]></description>
      <link>http://software.intel.com/en-us/articles/cross-compilation-using-intel-c-compiler-for-linux/#comment-44313</link>
      <pubDate>Fri, 04 Jun 2010 04:52:51 -0700</pubDate>
      <guid isPermaLink="true">http://software.intel.com/en-us/articles/cross-compilation-using-intel-c-compiler-for-linux/#comment-44313</guid>
    </item>
  </channel></rss>
