<?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>LPCXpresso IDE FAQsのトピックPorting Code from other toolchains</title>
    <link>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Porting-Code-from-other-toolchains/m-p/472797#M98</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generally where example code is provided for another toolchain it will normally port across to the LPCXpresso IDE fairly easily. Simply create a new project within the LPCXpresso IDE, then copy the required source files across.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A few things to watch:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Sometimes, depending upon the original project, you may need to produce your own linker script, rather than use the default linker script created automatically by the LPCXpresso IDE. Details of how to go about doing this can be found in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389125" data-objecttype="1" href="https://community.nxp.com/thread/389125"&gt;Using your own linker scripts&lt;/A&gt;.&lt;/LI&gt;&lt;LI&gt;There are sometimes slight changes required to sources due to "extensions to the C language" used by source code. Typical examples are:&lt;UL&gt;&lt;LI&gt;How packed structures are written. More details in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389103" data-objecttype="1" href="https://community.nxp.com/thread/389103"&gt;Packed Structures&lt;/A&gt;.&lt;/LI&gt;&lt;LI&gt;The &lt;TT&gt;'at'&lt;/TT&gt; attribute described in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389115" data-objecttype="1" href="https://community.nxp.com/thread/389115"&gt;Problems compiling "__attribute__((at"&lt;/A&gt;.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Some examples may contain conditionally compiling code blocks &lt;STRONG&gt;(&lt;TT&gt;#ifdef .. #else .. #endif&lt;/TT&gt;)&lt;/STRONG&gt;. You may need to check the actual source code, any supplied documentation, or project/make files from the original target toolchain, to confirm what symbols you need to define to get the code to build appropriately for your needs.&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Mar 2016 22:28:30 GMT</pubDate>
    <dc:creator>lpcware-support</dc:creator>
    <dc:date>2016-03-31T22:28:30Z</dc:date>
    <item>
      <title>Porting Code from other toolchains</title>
      <link>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Porting-Code-from-other-toolchains/m-p/472797#M98</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Generally where example code is provided for another toolchain it will normally port across to the LPCXpresso IDE fairly easily. Simply create a new project within the LPCXpresso IDE, then copy the required source files across.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A few things to watch:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Sometimes, depending upon the original project, you may need to produce your own linker script, rather than use the default linker script created automatically by the LPCXpresso IDE. Details of how to go about doing this can be found in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389125" data-objecttype="1" href="https://community.nxp.com/thread/389125"&gt;Using your own linker scripts&lt;/A&gt;.&lt;/LI&gt;&lt;LI&gt;There are sometimes slight changes required to sources due to "extensions to the C language" used by source code. Typical examples are:&lt;UL&gt;&lt;LI&gt;How packed structures are written. More details in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389103" data-objecttype="1" href="https://community.nxp.com/thread/389103"&gt;Packed Structures&lt;/A&gt;.&lt;/LI&gt;&lt;LI&gt;The &lt;TT&gt;'at'&lt;/TT&gt; attribute described in the FAQ &lt;A _jive_internal="true" data-containerid="11529" data-containertype="14" data-objectid="389115" data-objecttype="1" href="https://community.nxp.com/thread/389115"&gt;Problems compiling "__attribute__((at"&lt;/A&gt;.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Some examples may contain conditionally compiling code blocks &lt;STRONG&gt;(&lt;TT&gt;#ifdef .. #else .. #endif&lt;/TT&gt;)&lt;/STRONG&gt;. You may need to check the actual source code, any supplied documentation, or project/make files from the original target toolchain, to confirm what symbols you need to define to get the code to build appropriately for your needs.&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Mar 2016 22:28:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPCXpresso-IDE-FAQs/Porting-Code-from-other-toolchains/m-p/472797#M98</guid>
      <dc:creator>lpcware-support</dc:creator>
      <dc:date>2016-03-31T22:28:30Z</dc:date>
    </item>
  </channel>
</rss>

