<?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>S32KのトピックRe: ETAS OS's integration</title>
    <link>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1837305#M33589</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;the main difference between GHS and gcc is that GHS uses #pragma instead of __attribute__ in gcc. But in my opinion it is easy replace #pragmas by __attribude__ - if needed. .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can simply create new S32DS project, move your existing source code and fix errors reported by compiler.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 Mar 2024 13:08:26 GMT</pubDate>
    <dc:creator>jiri_kral</dc:creator>
    <dc:date>2024-03-28T13:08:26Z</dc:date>
    <item>
      <title>ETAS OS's integration</title>
      <link>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1836210#M33510</link>
      <description>&lt;P&gt;We are currently trying to integrate ETAS OS into S32DS project and compile using GCC instead of ETASOS' default GHS. I wonder which example project will&amp;nbsp;be easier that I should base my porting work on, and I would be appreciate it if there is any advice or guidance.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2024 09:41:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1836210#M33510</guid>
      <dc:creator>ZMY666777</dc:creator>
      <dc:date>2024-03-27T09:41:13Z</dc:date>
    </item>
    <item>
      <title>Re: ETAS OS's integration</title>
      <link>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1837217#M33579</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I am not familiar with ETAS OS. If the GCC is supported compiler then it will be quite simple.&lt;/P&gt;
&lt;P&gt;If you need to port from GHS to GCC, well, that would require a significant amount of effort.&lt;/P&gt;
&lt;P&gt;Not sure why you want to start from some example. I would start with blank project.&lt;/P&gt;
&lt;P&gt;You can also use GHS compiler within the S32DS instead of GCC.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 10:11:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1837217#M33579</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2024-03-28T10:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: ETAS OS's integration</title>
      <link>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1837305#M33589</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;the main difference between GHS and gcc is that GHS uses #pragma instead of __attribute__ in gcc. But in my opinion it is easy replace #pragmas by __attribude__ - if needed. .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can simply create new S32DS project, move your existing source code and fix errors reported by compiler.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 13:08:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/ETAS-OS-s-integration/m-p/1837305#M33589</guid>
      <dc:creator>jiri_kral</dc:creator>
      <dc:date>2024-03-28T13:08:26Z</dc:date>
    </item>
  </channel>
</rss>

