Transitioning from Intel® System Studio to the Intel® oneAPI Development Tools
The introduction of the Intel oneAPI development tools updates our approach to how we provide development tools for IoT Linux application development. Per the table below, you can see that the majority of the Intel System Studio tools are now part of one or more Intel oneAPI toolkits.
The Intel System Studio development tools are included in the following Intel oneAPI toolkits:
Intel® oneAPI Base Toolkit
Intel® oneAPI IoT Toolkit
Intel® System Bring-up Toolkit
A complete list of Intel oneAPI Toolkits can be found here:
The following table maps the Intel System Studio tools to their equivalent Intel oneAPI tools.
NOTE:
There are many additional tools in the Intel® oneAPI Base Toolkit that are not part of the Intel® System Studio 2020 suite of tools. When installing a oneAPI toolkit you are given the option to install only those tools that you actually need.
Intel® System Studio 2020 Tool |
Intel® oneAPI Equivalent Tool |
|---|---|
Intel® oneAPI Base Toolkit: |
|
Intel® oneAPI DPC++/C++ Compiler (dpcpp) |
|
Intel Compiler Library (pstl) |
Intel® oneAPI DPC++ Library (pstl, Boost.Compute and SYCL) |
Intel® oneAPI Collective Communications Library (ccl) |
|
Intel® Data Analytics Acceleration Library (daal) |
Intel® oneAPI Data Analytics Library (dal) |
Intel® oneAPI Deep Neural Networks Library (dnnl) |
|
Intel® Math Kernel Library (mkl) |
Intel® oneAPI Math Kernel Library (mkl) |
Intel® Threading Building Blocks (tbb) |
Intel® oneAPI Threading Building Blocks (tbb) |
Intel® oneAPI Video Processing Library (vpl) |
|
Intel® Integrated Performance Primitives (ipp) |
Intel® Integrated Performance Primitives (ipp) |
Intel® Advisor |
Intel® Advisor |
Intel® VTune(tm) Profiler |
Intel® VTune(tm) Profiler |
The GNU* Project Debugger (GDB) (gdb-ia) |
Intel® Distribution for GDB* (gdb-ia) |
Intel® Distribution for Python* |
|
Intel® DPC++ Compatibility Tool |
|
OpenCL(tm) Tools for Intel® System Studio Eclipse IDE |
Intel® FPGA Add-on for the oneAPI Base Toolkit |
Intel® oneAPI IoT Toolkit: |
|
Intel® oneAPI DPC++/C++ Compiler (dpcpp) |
|
Intel® C++ Compiler (icc) |
Intel® C++ Compiler Classic (icc) |
Intel System Studio Eclipse IDE |
Eclipse* IDE for C/C++ Developers |
IoT Connection Tools |
IoT Connection Tools |
Yocto Project* Application and Platform Development |
Linux* Kernel Build Tools |
Linux* IoT App Dev Using Containerized Toolchains |
|
Intel® Inspector |
Intel® Inspector |
Intel® System Bring-up Toolkit: |
|
Intel® System Debugger |
Intel® System Debugger |
Intel® Debug Extensions for WinDbg* |
Intel® Debug Extensions for WinDbg* |
OpenCL(tm) Tools for Visual Studio* |
|
Intel® VTune(tm) Profiler |
Intel® VTune(tm) Profiler |
Energy Analysis with Intel® SoC Watch |
Energy Analysis with Intel® SoC Watch |
For the most part, the equivalent oneAPI tools are simply updated or enhanced versions of the same tools delivered as part of the Intel System Studio (ISS) suite of tools. In some cases there is also a name change to some tools as they are identified in the Intel oneAPI Toolkits.
The most significant changes between ISS and the Intel oneAPI Toolkits are:
Renaming the Intel C++ Compiler to Intel C++ Compiler Classic.
Addition of the new Intel oneAPI DPC++ Compiler.
Changes to the list of supported IDEs and how they are supported.
That last bullet is the most significant, and is the focus of this documentation.
Changes to Intel System Studio IDE support
One of the key changes between ISS and oneAPI has to do with how we support the Eclipse IDE for C/C++ Developers workflow for IoT developers. These changes relate to the custom Linux* cross-platform development workflow that was included in the ISS distribution of Eclipse. That cross-development workflow relied heavily on the use of Docker* containers to implement a Linux development environment for use on Windows, Linux and macOS development systems.
The custom, cross-development Eclipse plugins that are part of ISS have not been migrated to the oneAPI IoT Toolkit. Instead, the IoT Toolkit relies on existing standard Eclipse for C/C++ Developer (CDT) plugins and Visual Studio Code* (VS Code) to provide equivalent workflows. In the years since the ISS cross-development plugins were originally created there have been significant advancements to support development on remote Linux systems, especially for users of Windows 10 and users of the popular cross-platform VS Code editor.
The oneAPI IoT Toolkit only supports the use of Eclipse on Linux hosts. For those Linux IoT application developers who need a cross-platform development workflow that supports Windows, Linux, or macOS hosts, we recommend using the Visual Studio Code remote Linux development tools.
The following chapters will describe how to migrate an existing ISS Eclipse project to:
an Eclipse IDE for C/C++ Developers project
a command-line project
All of the above bullets assume you are moving from the use of Eclipse to develop Linux projects using the ISS container-based workflow.
See Also
*Other names and brands may be claimed as the property of others.