<?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 compiling standalone applications alone in PowerQUICC Processors</title>
    <link>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561296#M1591</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Currently Hello_world.c gets compiled alone with uboot. What should we do to compile hello world alone without compiling uboot?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Aug 2016 10:55:34 GMT</pubDate>
    <dc:creator>garimella</dc:creator>
    <dc:date>2016-08-02T10:55:34Z</dc:date>
    <item>
      <title>compiling standalone applications alone</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561296#M1591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Currently Hello_world.c gets compiled alone with uboot. What should we do to compile hello world alone without compiling uboot?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Aug 2016 10:55:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561296#M1591</guid>
      <dc:creator>garimella</dc:creator>
      <dc:date>2016-08-02T10:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: compiling standalone applications alone</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561297#M1592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;Look at the following page install standalone toolchain:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Ffreescale.sdlproducts.com%2FLiveContent%2Fcontent%2Fen-US%2FQorIQ_SDK%2FGUID-16DBC8E2-9A18-4867-9BE1-168062EF31C4" rel="nofollow" target="_blank"&gt;https://freescale.sdlproducts.com/LiveContent/content/en-US/QorIQ_SDK/GUID-16DBC8E2-9A18-4867-9BE1-168062EF31C4&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;Build and install the standalone toolchain with Yocto:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$ source ./fsl-setup-poky -m &amp;lt;machine&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$ bitbake fsl-toolchain&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$ cd build_&amp;lt;machine&amp;gt;_release/tmp/deploy/sdk &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$ ./fsl-networking-eglibc-&amp;lt;host-system&amp;gt;-&amp;lt;core&amp;gt;-toolchain-&amp;lt;release&amp;gt;.sh&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;Note: The default installation path for standalone toolchain is /opt/fsl-networking/. The install folder can be specified during the installation procedure.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;source /opt/fsl-qoriq/2.0/environment-setup-aarch64-fsl-linux&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;Check result of "source" command. Use "$PATH" command. The "source" command should add path to gcc compiler. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;You should see similar message:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$PATH&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;bash: /opt/fsl-qoriq/2.0/sysroots/x86_64-fslsdk-linux/usr/bin:/opt/fsl-qoriq/2.0/sysroots/x86_64-fslsdk-linux/usr/bin/../x86_64-fslsdk-linux/bin:/opt/fsl-qoriq/2.0/sysroots/x86_64-fslsdk-linux/usr/bin/aarch64-fsl-linux:/opt/fsl-qoriq/2.0/sysroots/x86_64-fslsdk-linux/usr/bin/aarch64-fsl-linux-uclibc:/opt/fsl-qoriq/2.0/sysroots/x86_64-fslsdk-linux/usr/bin/aarch64-fsl-linux-musl:/ltib/QorIQ-SDK-V2.0-20160527-yocto/sources/poky/scripts:/ltib/QorIQ-SDK-V2.0-20160527-yocto/sources/poky/bitbake/bin:/ltib/Freescale-Linux-SDK-for-LS1021A-IOT-Rev2-v0.4-20150907-yocto.iso/poky/scripts:/ltib/Freescale-Linux-SDK-for-LS1021A-IOT-Rev2-v0.4-20150907-yocto.iso/poky/bitbake/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="font-size: 10.0pt; background: white;"&gt;$CC test.c --sysroot=/opt/fsl-qoriq/2.0/sysroots/aarch64-fsl-linux&amp;nbsp; -o test.elf&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Pavel Chubakov&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2016 04:53:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561297#M1592</guid>
      <dc:creator>Pavel</dc:creator>
      <dc:date>2016-08-04T04:53:07Z</dc:date>
    </item>
    <item>
      <title>Re: compiling standalone applications alone</title>
      <link>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561298#M1593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks but not work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2019 11:42:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/PowerQUICC-Processors/compiling-standalone-applications-alone/m-p/561298#M1593</guid>
      <dc:creator>love_hate_and_repeat</dc:creator>
      <dc:date>2019-06-27T11:42:07Z</dc:date>
    </item>
  </channel>
</rss>

