I can successfully build a Yocto image and produce the proper SDK using bitbake. I have used the generated script to populate the sdk including the sysroot to /opt/poky-edison/1.7.3/.... Additionally, I have installed, and successfully used Intel System Studio IOT Edition to build example code and use it.
I see that System Studio uses docker to execute in a container the toolchain including the sysroot. Why do we need docker if we are on Linux? How do I target my SDK rather than whatever one is in the docker container? Do I need to make a new docker container? Is so, how? Do I need to modify the existing container? Again, if so, how? Can I invoke the toolchain and sysroot locally without docker at all? If so, how?
It seems that older versions of the IDE, when it was called Intel IoT Developer Kit, did not use docker and the sysroot could be specified directly in the settings.
Any help would be greatly appreciated.
In regard to your concern about Intel® System Studio for further assistance, I would like to kindly refer you to their direct support contact at the following link:
I am looking forward to hearing from you.
Thank you for contacting us, we'll do our best to help you answer your questions.
I'm not sure if this is what you were looking for but go ahead and try with these steps: Go to Project>Properties. Click C/C++ Build > Settings. You need to select the sysroot from the Edison SDK. Then, click C/C++ Build > Environment and select the path to the Edison SDK. Now, you should be able to build applications. There's one last step where you need to set the compilation option. You can see step 4 of https://software.intel.com/en-us/articles/use-intel-system-studio-to-develop-for-intel-edison https://software.intel.com/en-us/articles/use-intel-system-studio-to-develop-for-intel-edison for more information. At the end of the link we mentioned is also a guide to Build and Debug Applications with lots of useful information.
Let us know if you find this is what you were looking for.
Thanks for the input. I think I may know where the discrepancy is with all of this. When you import an IoT project into Intel System Studio IoT Edition, it uses the IoT Poky 32-Bit GCC toolchain with the IoT Internal Builder. This uses docker and a preconfigured docker container. My suspicion is that I need an entirely different tool-chain and builder selected. Maybe I need to select Cross-GCC? The confusion is coming from the fact that much of the documentation references Intel System Studio and not the IoT edition.
Do you use the tool-chain mentioned above? If not, what tool-chain do you have selected? Is there anyway you can send me an example project that has all the settings configured?
When we first configured the ISS we followed the installation guide and installed Docker Toolbox using the preconfigured settings. The other tests we've done where we needed to setup a toolchain we've always used the one in the Build and Debug guide. I haven't used an alternative toolchain but you can try to use the cross-gcc option to see if you get positive results.
Feel free to share your results.
The guide I was referring to is the one that can be found at the bottom of this website https://software.intel.com/en-us/articles/build-and-debug-applications-for-intel-edison-with-intel-s... https://software.intel.com/en-us/articles/build-and-debug-applications-for-intel-edison-with-intel-s... . The guide applies to ISS 2015. It may not be the latest one but, some key concepts still apply. The latest documentation on the ISS IoT Edition can be found here https://software.intel.com/en-us/iot/tools-ide/ide/iss-iot-edition https://software.intel.com/en-us/iot/tools-ide/ide/iss-iot-edition .
We have an update for your case.
It should be possible to setup ISS IoT Edition with the Intel Compiler, nevertheless, this might not be a trivial task on the latest version of ISS IoT Edition. You would have to change the environment variables, the commands for cross-compilation under settings, change some configurations of the Tool Chain Editor, etc.. However, an easier more trivial alternative would be to use a previous version of the Intel System Studio.
We have successfully linked the blink project to use the local SDK (build from source) by changing the POKY_HOME Environment Variable to point to the local SDK path /opt/poky-edison/1.7.3/sysroots/core2-32-poky-linux (or whichever location customer has set the SDK to). The previous version of the ISS is available to download here https://downloadcenter.intel.com/download/26028.
Please let us know if you run into issues when setting this up.