<?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: Is it possible to call a .dll file built by Fortran without in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800912#M37646</link>
    <description>There is a file fredist.txt in the docs folder that lists all the redistributable files.&lt;BR /&gt;</description>
    <pubDate>Thu, 31 Aug 2006 20:48:31 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2006-08-31T20:48:31Z</dc:date>
    <item>
      <title>Is it possible to call a .dll file built by Fortran without "libifcoremd.dll" ..?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800908#M37642</link>
      <description>When a .exe file calls a .dll file built by Fortran, must I provide&lt;BR /&gt;
the "libifcoremd.dll" and some other .dll files (in IVF installed folder) in a search path? &lt;BR /&gt;
&lt;BR /&gt;
That means whether I must install IVF if I use a .exe to call a .Dll file built by Fortran?&lt;BR /&gt;
Thanks a lot!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Aug 2006 17:09:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800908#M37642</guid>
      <dc:creator>lyricx</dc:creator>
      <dc:date>2006-08-30T17:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to call a .dll file built by Fortran without</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800909#M37643</link>
      <description>1) It depends. The default setting for a dll is to use dll version run-time library. If you change that (Project/Properties/Fortran/Libraries/Run-time library), you will get the required RTL functions embedded in the dll instead. That &lt;B&gt;might &lt;/B&gt;cause problems if the .exe is also built using IVF and certain conditions are met (.exe and .dll share I/O unit numbers and/or do mutual allocation/deallocation of memory, so Steve discourages that), but it's fairly unlikely.&lt;BR /&gt;&lt;BR /&gt;2) Even if you use dll version of RTL, it's sufficient just to copy libifcoremd.dll to the .exe's folder or somewhere in PATH to the target computer.&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Aug 2006 19:15:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800909#M37643</guid>
      <dc:creator>Jugoslav_Dujic</dc:creator>
      <dc:date>2006-08-30T19:15:15Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to call a .dll file built by Fortran without</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800910#M37644</link>
      <description>For your 2), Can I copy the .dll files required by our .exe called .dll &lt;BR /&gt;
in our owner folder if I am planning to commercialize our software?&lt;BR /&gt;
Is this behavior violate copyright? or we need negotiate with Intel? Thanks a lot for clarification!&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Aug 2006 09:34:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800910#M37644</guid>
      <dc:creator>lyricx</dc:creator>
      <dc:date>2006-08-31T09:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to call a .dll file built by Fortran without</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800911#M37645</link>
      <description>To the best of my knowledge (I'm not an Intel employee), yes, you're allowed to distribute it with your software (Release versions only, not the ones with rtd.dll or mdd.dll suffix).&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Aug 2006 17:45:42 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800911#M37645</guid>
      <dc:creator>Jugoslav_Dujic</dc:creator>
      <dc:date>2006-08-31T17:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to call a .dll file built by Fortran without</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800912#M37646</link>
      <description>There is a file fredist.txt in the docs folder that lists all the redistributable files.&lt;BR /&gt;</description>
      <pubDate>Thu, 31 Aug 2006 20:48:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800912#M37646</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2006-08-31T20:48:31Z</dc:date>
    </item>
    <item>
      <title>Re: Is it possible to call a .dll file built by Fortran without</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800913#M37647</link>
      <description>Thanks a lot for your clarifications!&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Sep 2006 10:47:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Is-it-possible-to-call-a-dll-file-built-by-Fortran-without-quot/m-p/800913#M37647</guid>
      <dc:creator>lyricx</dc:creator>
      <dc:date>2006-09-01T10:47:54Z</dc:date>
    </item>
  </channel>
</rss>

