Getting Started with Application Development Using Intel® System Studio 2018 for macOS* Host and Linux* OS Target

Explore the Build Components

  • Intel® C++ Compiler: Develop optimized applications in the Eclipse* IDE
  • Intel® Math Kernel Library: Improve application performance
  • Intel® Threading Building Blocks: Optimize embedded solutions for multi-core architectures
  • Intel® Integrated Performance Primitives: Speed up signal and image processing, data compression, string manipulation, and more
  • Intel® Data Analytics Acceleration Library: Boost machine learning and big data analytics performance

Launch Intel® System Studio

For a Linux* target, run one of the following launcher scripts:

  • Linux host: /opt/intel/system_studio_2018/iss_ide_eclipse-launcher.sh

  • Windows* host: C:\IntelSWTools\system_studio_2018\iss_ide_eclipse-launcher.bat

  • macOS* host: /opt/intel/system_studio_2018/iss_ide_eclipse-launcher.sh

System Requirements

Release Notes

Create a C/C++ Project for Building in a Container and Running on Linux*

Intel® System Studio provides fully configured compile and build toolchains in the form of Docker containers. These are particularly useful for creating Linux* based IoT applications using a fast edit, debug, and deploy process.

Step 1: Ensure Docker is installed

Before creating a new project, make sure Docker is installed and configured on your machine.

Step 2: Create a project

  1. Choose File > New > Project to start the new project wizard.

  2. Expand the Application Development folder and select C/C++ project for building in a container and running on Linux.

  3. Click Next.
  4. In the Select a Docker toolchain list, select your target Linux operating system. Click Next.

  5. Type a name for the project in the Name field. In the Examples list, browse for and select the type of project to create, such as C++ > Basic > Hello World.

  6. Click Finish.

  7. If a notification that the platform support is not yet installed and must be downloaded appears, click Yes. Docker displays the notification when you use a specific container for the first time.

    Your project is created and displayed.

Step 3: Connect your device

 

CAUTION

When you connect to your target system this way, Intel System Studio copies a Target Communication Framework (TCF) agent to your target, which is listening for connections from any computer on your local network. The IDE target connection dialog asks for authentication credentials to facilitate transferring and starting the TCF agent on your target device; however, once running, the TCF agent does NOT require authentication to perform its actions. Therefore, any user that has network access to your target device can connect to it and use the TCF agent to run arbitrary code on your target device.

 

  1. Make sure your target device is physically connected to your host system and functioning properly.

    Note

    If your target is QEMU, start the QEMU simulator in your project directory by entering the command $ runqemu qemux86-64 nographic. When prompted, run ipconfig to get the IP address.
  2. Before you run or debug on a remote Linux* target, you may need to configure TCF connection options to allow access not commonly granted to normal users. If you are behind a firewall, you also need to configure the Intel® System Studio proxy. For instructions, see Prepare a remote Linux* target and then return here to continue connecting your device.

  3. Click the New Connection drop-down list in the toolbar.

  4. Select Connection for container based C/C++ applications or Java applications and click Next.

  5. Create your connection and then click Next:
    1. Name for the connection in the Connection name field.
    2. Name of the board or IP address in the Address field.
  6. When prompted, provide the appropriate credentials to access your device. Click OK.

Step 4: Run and debug a project

  1. From the Run drop-down list in the toolbar, select the name of your project.

  2. If a warning message about host authenticity displays, click Yes to upload and run your project.

  3. Your project runs. If the project does not exit automatically, click the red Terminate icon from the Console panel to stop the process.

  4. To debug, click the Debug drop-down list in the toolbar and select the name of your project.

For more information about creating C/C++ projects, see Developing C/C++ Projects with Intel System Studio.

 

Find More

Resource Description

Code Samples and Tutorials

Intel provides downloadable sample code and tutorials, which guide a new user through the basic product features: The sample code illustrates common scenarios, and the corresponding tutorials show how the build tools can be used to create and optimize code.

Intel® System Studio Get Started

Links to Getting Started Guides for all Intel® System Studio components

Intel System Studio Featured Documentation

Links to articles that address a wide range of Intel System Studio topics

Developing C/C++ Projects with Intel System Studio

Additional information about developing C/C++ projects; for example, managing projects and connections and troubleshooting tips.

Developing Wind River Linux* Applications with Intel System Studio

Information about developing Wind River Linux* applications.

Developing Java* Projects with Intel® System Studio.

Information about developing Java* projects.

Intel System Studio Log Files

Intel System Studio writes pairs of log files to a subdirectory in /tmp. The subdirectory name has the format iss_env_$USER_$TIMESTAMP. The iss_env.log file contains environment settings. The eclipse.log file contains a session log. For example: /tmp/iss_env_auser_20171025141933/eclipse.log and /tmp/iss_env_auser_20171025141933/iss_env.log

The Intel System Studio installer writes log files to the system temp directory ( echo $TMPDIR), one for the user and one for root (when the installer is run with sudo). These log file names start with intel.pset, end with a timestamp, and have the extension *.log. To locate these files, type cd $TMPDIR, then look for files matching the pattern. For example: $TMPDIR/intel.pset.auser.samukawi_mobl1.my.corp.domain_10.25.22.00.13.2017.log

Installing Docker* for Intel® System Studio 2018

Installing Docker* for Intel® System Studio - macOS* Host

Installing Docker* for Intel® System Studio - Linux* Host

Installing Docker* for Intel® System Studio - Windows* Host

Additional Documentation

Use the online documentation for the latest content.

A downloadable ZIP file containing all Intel® System Studio documentation is available for offline use from https://software.intel.com/en-us/articles/download-documentation-intel-system-studio-current-previous.

Intel® System Studio Product Page

Visit this page for support and the latest online documentation.

 

Prerequisite: Remote Linux* target setup

Before you develop applications on Linux*, macOS*, or Windows* hosts to run on remote Linux systems, you must:

  • Configure TCF connection options
  • Configure the Intel® System Studio proxy

Configure TCF connection options

For a specific target, configure TCF connection options to allow access not commonly granted to normal users. For example, MRAA I/O operations require special permissions to UNIX character devices and sysfs.

These steps must be performed once per target.

Click here for instructions to configure TCF connection options in Intel® System Studio.

Configure the Intel® System Studio proxy

If you are working behind a proxy server, you may need to configure the Intel System Studio (Eclipse*) proxy. Follow these Eclipse proxy instructions to set your Intel System Studio proxy. If you're on an open network, skip these steps.

Consult your network admin to determine the correct proxy settings for your work environment.

Note

We recommend that you leave the SOCKS proxy setting empty in the Eclipse proxy settings. In some proxy environments, setting the Eclipse SOCKS proxy may interfere with the ability of Intel System Studio to access Internet resources. In this case, the specific error messages provided by Intel System Studio may be misleading. This is a known problem with Eclipse.

 

BACK TO CONNECT INSTRUCTIONS

 

Legal Information

Intel, the Intel logo, Intel Atom, Intel Core, Intel Xeon Phi, VTune and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries.

*Other names and brands may be claimed as the property of others.

Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft Corporation in the United States and/or other countries.

Copyright 2014-2018 Intel Corporation.

This software and the related documents are Intel copyrighted materials, and your use of them is governed by the express license under which they were provided to you (License). Unless the License provides otherwise, you may not use, modify, copy, publish, distribute, disclose or transmit this software or the related documents without Intel's prior written permission.

This software and the related documents are provided as is, with no express or implied warranties, other than those that are expressly stated in the License.

有关编译器优化的更完整信息,请参阅优化通知