<?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 compile ipp-samples on windows with debug info in Intel® Integrated Performance Primitives</title>
    <link>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820096#M4642</link>
    <description>VC90.pdb? I used to think, that it must be &lt;EXECUTABLE_NAME&gt;.pdb, where debug information is stored. I've done the following (speech samples make file from some of 7.0 samples):&lt;DIV&gt;Makefile:line 64: CFLAGS = /W4 /Od /Zi $(M_FLAG) /EHsc /GS /c&lt;/DIV&gt;&lt;DIV&gt;Makefile:line 152:LINK_CMD = $(LINK32) $(LINK_MOD) $(SYBSYSTEM_MODE) $(ADD_LINK_OPT) /DEBUG /nodefaultlib:"libcmt.lib" \&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;As a result I've got 5 exe files + 5 corresponding pdb files in samples' output _bin directory. I believe that's what we need for debugging. VS debugger works on that executables.&lt;BR /&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Sergey&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/EXECUTABLE_NAME&gt;</description>
    <pubDate>Mon, 21 May 2012 05:53:17 GMT</pubDate>
    <dc:creator>Sergey_K_Intel</dc:creator>
    <dc:date>2012-05-21T05:53:17Z</dc:date>
    <item>
      <title>compile ipp-samples on windows with debug info</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820093#M4639</link>
      <description>Hello,&lt;DIV&gt;is there a way to compile a "debug" version of ipp-samples (libspeech most notably) with debug symbols with VS2008 (and 2010)?&lt;/DIV&gt;&lt;DIV&gt;if i compile the samples with build_ia32.bat cl9 i get only a "release" version&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;thanks&lt;/DIV&gt;</description>
      <pubDate>Fri, 18 May 2012 08:07:26 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820093#M4639</guid>
      <dc:creator>Francesco_Lamonica</dc:creator>
      <dc:date>2012-05-18T08:07:26Z</dc:date>
    </item>
    <item>
      <title>compile ipp-samples on windows with debug info</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820094#M4640</link>
      <description>Hi Francesco,&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;Try to modify "Makefile" for the project(s). There should be line "CFLAGS = ...". Find "/O2" in this line and change it to "/Od /Zi", or to "/O2 /Zi" if you need to keep optimization and add debug information to optimized code.&lt;/DIV&gt;&lt;DIV&gt;Then, add "/DEBUG" to "LINK_CMD" line. Rebuild the sample with "build_ia32.bat cl9" command.&lt;/DIV&gt;&lt;DIV&gt;You should get debug-ability finally.&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Sergey&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 18 May 2012 13:47:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820094#M4640</guid>
      <dc:creator>Sergey_K_Intel</dc:creator>
      <dc:date>2012-05-18T13:47:13Z</dc:date>
    </item>
    <item>
      <title>compile ipp-samples on windows with debug info</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820095#M4641</link>
      <description>Hi Sergey,&lt;DIV&gt;thanks for your answer, now i have a .lib with debugging info, however it did not create any vc90.pdb file (that is usually created when compiling in "debug" from VS) is that, somehow, included in the .lib?&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;thanks&lt;/DIV&gt;</description>
      <pubDate>Fri, 18 May 2012 16:00:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820095#M4641</guid>
      <dc:creator>Francesco_Lamonica</dc:creator>
      <dc:date>2012-05-18T16:00:06Z</dc:date>
    </item>
    <item>
      <title>compile ipp-samples on windows with debug info</title>
      <link>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820096#M4642</link>
      <description>VC90.pdb? I used to think, that it must be &lt;EXECUTABLE_NAME&gt;.pdb, where debug information is stored. I've done the following (speech samples make file from some of 7.0 samples):&lt;DIV&gt;Makefile:line 64: CFLAGS = /W4 /Od /Zi $(M_FLAG) /EHsc /GS /c&lt;/DIV&gt;&lt;DIV&gt;Makefile:line 152:LINK_CMD = $(LINK32) $(LINK_MOD) $(SYBSYSTEM_MODE) $(ADD_LINK_OPT) /DEBUG /nodefaultlib:"libcmt.lib" \&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;As a result I've got 5 exe files + 5 corresponding pdb files in samples' output _bin directory. I believe that's what we need for debugging. VS debugger works on that executables.&lt;BR /&gt;Regards,&lt;/DIV&gt;&lt;DIV&gt;Sergey&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/EXECUTABLE_NAME&gt;</description>
      <pubDate>Mon, 21 May 2012 05:53:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Integrated-Performance/compile-ipp-samples-on-windows-with-debug-info/m-p/820096#M4642</guid>
      <dc:creator>Sergey_K_Intel</dc:creator>
      <dc:date>2012-05-21T05:53:17Z</dc:date>
    </item>
  </channel>
</rss>

