<?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: C Compile Flags in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887316#M35028</link>
    <description>mephisto890,&lt;BR /&gt;&lt;BR /&gt;I believe that you will find this is the /PREPROCESS_ONLY qualifier. Check the HELP text for how to direct the resulting output file.&lt;BR /&gt;&lt;BR /&gt;I would recommend checking the HELP text for the CC command to see if any of the other qualifiers are appropriate for your situation.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
    <pubDate>Thu, 26 Oct 2006 09:59:44 GMT</pubDate>
    <dc:creator>Robert Gezelter</dc:creator>
    <dc:date>2006-10-26T09:59:44Z</dc:date>
    <item>
      <title>C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887315#M35027</link>
      <description>I have C source code currently running on VMS 7.2 and we use the DEC C 6.0 compiler.&lt;BR /&gt;We use the Vax C compatibility switch to compile the code as well.&lt;BR /&gt;&lt;BR /&gt;We are having some problems with the include files during compilation.&lt;BR /&gt;&lt;BR /&gt;I want to see all the include files during the precomipled phase to create a single file for compile analysis.  In ANSI C, the developer would set a flag to create a .i or .p file which has all the include file references in the source code.&lt;BR /&gt;&lt;BR /&gt;I am search for a like precompile FLAG to create a similier file on the VMS environment we are currently working on.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance.</description>
      <pubDate>Thu, 26 Oct 2006 09:55:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887315#M35027</guid>
      <dc:creator>mephisto890</dc:creator>
      <dc:date>2006-10-26T09:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887316#M35028</link>
      <description>mephisto890,&lt;BR /&gt;&lt;BR /&gt;I believe that you will find this is the /PREPROCESS_ONLY qualifier. Check the HELP text for how to direct the resulting output file.&lt;BR /&gt;&lt;BR /&gt;I would recommend checking the HELP text for the CC command to see if any of the other qualifiers are appropriate for your situation.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Thu, 26 Oct 2006 09:59:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887316#M35028</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2006-10-26T09:59:44Z</dc:date>
    </item>
    <item>
      <title>Re: C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887317#M35029</link>
      <description>Maybe this will do the task:&lt;BR /&gt;&lt;BR /&gt;$ CC /LIST/SHOW=INCLUDE ...&lt;BR /&gt;&lt;BR /&gt;This will produce a listing with all #include included.&lt;BR /&gt;&lt;BR /&gt;For more see: $ HELP CC /SHOW&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Thu, 26 Oct 2006 10:13:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887317#M35029</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2006-10-26T10:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887318#M35030</link>
      <description>Robert.....&lt;BR /&gt;&lt;BR /&gt;Would I include the /PREPROCESS_ONLY flag in the make file right???</description>
      <pubDate>Thu, 26 Oct 2006 10:53:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887318#M35030</guid>
      <dc:creator>mephisto890</dc:creator>
      <dc:date>2006-10-26T10:53:33Z</dc:date>
    </item>
    <item>
      <title>Re: C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887319#M35031</link>
      <description>With the /PREPROCESS_ONLY the compiler executes only the preprocess phase and will create a preprocessed file (no # commands except #line).&lt;BR /&gt;&lt;BR /&gt;With the /LIST/SHOW the compiler creates the object file (.OBJ) and a listing file (.LIS).&lt;BR /&gt;&lt;BR /&gt;So it depends on yours make file. If some parts depends on created object files that parts of make will not execute.&lt;BR /&gt;&lt;BR /&gt;Bojan</description>
      <pubDate>Thu, 26 Oct 2006 11:10:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887319#M35031</guid>
      <dc:creator>Bojan Nemec</dc:creator>
      <dc:date>2006-10-26T11:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: C Compile Flags</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887320#M35032</link>
      <description>I use "/show = (all,nomessages)", to get the&lt;BR /&gt;macro expansions, too.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; [...] In ANSI C [...]&lt;BR /&gt;&lt;BR /&gt;You seem to be coming from UNIX.  Around here,&lt;BR /&gt;we can get onject files and compiler listings&lt;BR /&gt;in one pass.</description>
      <pubDate>Thu, 26 Oct 2006 11:22:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/c-compile-flags/m-p/3887320#M35032</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2006-10-26T11:22:36Z</dc:date>
    </item>
  </channel>
</rss>

