<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Output object files as *.o instead of *.obj in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Output-object-files-as-o-instead-of-obj/m-p/827133#M50656</link>
    <description>&lt;P&gt;I don't believe there's a compiler option. As the usual reason for doing this is to support a degree of Makefile portability, we may accomplish itby addingMakefile rules for compilers whichbuild .obj e.g.&lt;/P&gt;
&lt;P&gt;.f.o:&lt;/P&gt;
&lt;P&gt;$(FC) $(FFLAGS) -c $*.f&lt;/P&gt;
&lt;P&gt;mv $*.obj $*.o&lt;/P&gt;
&lt;P&gt;Consequences of this usage vary between 32-bit and 64-bit Windows. It is also possible to set up the entire Makefile with names for object and exe extension, so as to switch them when switching compilers and OS.&lt;/P&gt;
&lt;P&gt;I think that either of these schemes are considered to be the property of the 5% fringe of Windows developers who develop for multiple operating systems and don't get cooperation from software tools vendors.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Mar 2007 13:59:22 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2007-03-16T13:59:22Z</dc:date>
    <item>
      <title>Output object files as *.o instead of *.obj</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Output-object-files-as-o-instead-of-obj/m-p/827132#M50655</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;
&lt;P&gt;May I know if it's possible to generate object file with extension .o instead of .obj automatically through some options in the compiler?&lt;/P&gt;
&lt;P&gt;I can't seem to find it.&lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2007 09:06:07 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Output-object-files-as-o-instead-of-obj/m-p/827132#M50655</guid>
      <dc:creator>Wee_Beng_T_</dc:creator>
      <dc:date>2007-03-16T09:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: Output object files as *.o instead of *.obj</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Output-object-files-as-o-instead-of-obj/m-p/827133#M50656</link>
      <description>&lt;P&gt;I don't believe there's a compiler option. As the usual reason for doing this is to support a degree of Makefile portability, we may accomplish itby addingMakefile rules for compilers whichbuild .obj e.g.&lt;/P&gt;
&lt;P&gt;.f.o:&lt;/P&gt;
&lt;P&gt;$(FC) $(FFLAGS) -c $*.f&lt;/P&gt;
&lt;P&gt;mv $*.obj $*.o&lt;/P&gt;
&lt;P&gt;Consequences of this usage vary between 32-bit and 64-bit Windows. It is also possible to set up the entire Makefile with names for object and exe extension, so as to switch them when switching compilers and OS.&lt;/P&gt;
&lt;P&gt;I think that either of these schemes are considered to be the property of the 5% fringe of Windows developers who develop for multiple operating systems and don't get cooperation from software tools vendors.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2007 13:59:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Output-object-files-as-o-instead-of-obj/m-p/827133#M50656</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2007-03-16T13:59:22Z</dc:date>
    </item>
  </channel>
</rss>

