<?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 C Program in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1740683#M4705</link>
    <description>&lt;P&gt;ST make a sensor called the Sensor Tile Box Pro.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It has a C++ program for accessing the box over a USB connection and it will work at 8000 cycles per second.&amp;nbsp; If I use the C# method I get 8 cycles per second.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The C++ program is supplied as an EXE file, whoever wrote it has no idea about getting data into a form for FFT and other analysis.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They provide a main.cpp and a main.h , a make list file and the c++ dll's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I use cmake it tells me there are no VC 1.45 versions on the computer, which cannot be correct as I have all of latest VS and oneapi installed.&amp;nbsp; I forward the program to VS 2026 insider and it tells me after I select the Intel Compiler&amp;nbsp;that it cannot find the "log.h" type files in the main.cpp.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a trick to getting make files to work with the intel compiler?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please do not say ask ST.COM that is a path to a long run of no answers.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;My apologies, I prefer Intel Fortran but calling C++ dll's from Fortran using dumpbin to look inside is a skill I have no desire to learn.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 12 Mar 2026 22:28:59 GMT</pubDate>
    <dc:creator>JohnNichols</dc:creator>
    <dc:date>2026-03-12T22:28:59Z</dc:date>
    <item>
      <title>C Program</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1740683#M4705</link>
      <description>&lt;P&gt;ST make a sensor called the Sensor Tile Box Pro.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It has a C++ program for accessing the box over a USB connection and it will work at 8000 cycles per second.&amp;nbsp; If I use the C# method I get 8 cycles per second.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The C++ program is supplied as an EXE file, whoever wrote it has no idea about getting data into a form for FFT and other analysis.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They provide a main.cpp and a main.h , a make list file and the c++ dll's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I use cmake it tells me there are no VC 1.45 versions on the computer, which cannot be correct as I have all of latest VS and oneapi installed.&amp;nbsp; I forward the program to VS 2026 insider and it tells me after I select the Intel Compiler&amp;nbsp;that it cannot find the "log.h" type files in the main.cpp.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a trick to getting make files to work with the intel compiler?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please do not say ask ST.COM that is a path to a long run of no answers.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;My apologies, I prefer Intel Fortran but calling C++ dll's from Fortran using dumpbin to look inside is a skill I have no desire to learn.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Mar 2026 22:28:59 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1740683#M4705</guid>
      <dc:creator>JohnNichols</dc:creator>
      <dc:date>2026-03-12T22:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: C Program</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1740879#M4707</link>
      <description>&lt;P&gt;I took a look at the STMicroelectronics web site and their ST SensorTile.box PRO. I have no idea where to find any of the EXE or DLL files that you refer to, nore the main.cpp and main.h files.&lt;BR /&gt;&lt;BR /&gt;Can you please provide further details so as to make it possible to find all the software bits and pieces that you are referring to? I'm curious about working with this device using Intel Fortran and C++.&lt;/P&gt;</description>
      <pubDate>Sun, 15 Mar 2026 02:41:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1740879#M4707</guid>
      <dc:creator>witwald</dc:creator>
      <dc:date>2026-03-15T02:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: C Program</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1742766#M4723</link>
      <description>&lt;LI-CODE lang="cpp"&gt;#if ! (defined _SYS_TIME_H &amp;amp;&amp;amp; defined _WINSOCK_H)
/* The following definitions must be exposed both when &amp;lt;sys/time.h&amp;gt;
 * is included in its own right, and when it is included selectively
 * on behalf of &amp;lt;winsock.h&amp;gt;, but they must not be processed twice.
 */
struct timeval
{ /* Nominally a BSD or POSIX.1 structure, (with tv_sec declared as
   * time_t), but subverted by Microsoft with tv_sec declared as long,
   * to avoid __time32_t vs. __time64_t ambiguity; (tv_sec is ALWAYS
   * a 32-bit entity in Windows' use of this structure).  Addionally,
   * POSIX.1-2001 mandates that tv_usec should be suseconds_t, (which
   * is nominally an alias for long), but we retain long to maintain
   * consistency with Microsoft usage.
   */
  long tv_sec;		/* whole number of seconds in interval */
  long tv_usec; 	/* additional fraction as microseconds */
};&lt;/LI-CODE&gt;&lt;P&gt;This compiles in g++, but in Intel C++ I get an error on line 6, which is 55 in the code&amp;nbsp; it is from the time.h in gcc&lt;/P&gt;&lt;P&gt;expected a ';' on line 55.&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="cpp"&gt;int __cdecl __MINGW_NOTHROW gettimeofday
(struct timeval *__restrict__, void *__restrict__ /* tzp (unused) */);&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;same on Line 1.&amp;nbsp; I cannot see that the code is incorrect, even the AI comments say it is ok, and no one trusts them.&amp;nbsp;&lt;/P&gt;&lt;P&gt;help appreciated.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2026 02:48:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1742766#M4723</guid>
      <dc:creator>JohnNichols</dc:creator>
      <dc:date>2026-04-01T02:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: C Program</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1742787#M4724</link>
      <description>&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P&gt;Yeah, it’s a bit confusing at first.&lt;/P&gt;&lt;P&gt;For the &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;STMicroelectronics&lt;/SPAN&gt;&lt;/SPAN&gt; SensorTile.box PRO, those files (EXE, DLL, main.cpp) aren’t available separately. They’re usually inside the STM32CubeIDE firmware packages and example projects&lt;A href="https://514digitalco.com/web-development-in-houston" target="_self"&gt;.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Just download the board’s firmware/SDK and check the example folders you’ll find everything there.&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 01 Apr 2026 08:13:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1742787#M4724</guid>
      <dc:creator>misteralex</dc:creator>
      <dc:date>2026-04-01T08:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: C Program</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1743084#M4725</link>
      <description>&lt;P&gt;I understand the confusion, they deal with a wide range of customers and they have a huge staff, so standards are important, but inflexible.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got g++ working, For the ST program I took out all the unnecessary files and got it down to basics, I can open main.cpp in VS to edit it and make it look pretty and use the old fashioned batch file to make, wait and look at the output and then run the program.&amp;nbsp;&lt;/P&gt;&lt;P&gt;LOL I cannot upload Clip6 as it is too big for this site as a zip file.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can get the Intel version down to 3 errors, but those are beyond me.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here is the revised main, I have trimmed it down a bit.&amp;nbsp; The old was a bit bloated.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Apr 2026 14:31:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/C-Program/m-p/1743084#M4725</guid>
      <dc:creator>JohnNichols</dc:creator>
      <dc:date>2026-04-03T14:31:16Z</dc:date>
    </item>
  </channel>
</rss>

