Project Configuration#
From the Project Configuration window display, you can set the Project Name, Location, and Target IDE.
Project Name#
In the Project Name field, the default name of the sample project displays. You can use the default project name or type a unique name for the project in this field.
Project Location#
In the Location field, the default path for your workspace is listed.
If you work for a company that has source control, it is recommended that you change this location to the appropriate source-controlled folder. Workspaces contain metadata that is not appropriate for source control.
To change the location, uncheck the Use default location box and enter the path in the field below, or click the BROWSE button to navigate to your preferred location.
Project Files#
The With Project Files area has three options that describe how the project is created related to the files coming from the SDK:
Link to sources: For SDK developers only. This option creates links to every source file.
Link sdk and copy project sources: The recommended option, which is selected by default. This option copies links to the non-project-specific SDK files and copies the project-specific source files into the project group folder. Linking the SDK files tends to save disk space because duplicate files are not stored in multiple locations.
Copy contents: Copies all project-specific and non-project files into your project. This option is recommended if you are building the project in a CI/CD environment where you do not want to have Simplicity Studio installed, or if you want to create a standalone project.
Click the radio button at the left of the option name to select it.
Project Target IDE#
Makefile IDE: This option generates a Makefile-based project that can be built from the command line using GNU Make and the GCC toolchain.
The project includes:
A Simplicity Studio configuration file (.slcp) for managing software components
PROJECTNAME.Makefile and PROJECTNAME.project.mak build scripts
Support for peripheral and stack configuration using Simplicity Studio’s Project Configurator and Advanced Configurators (e.g., Pintool, GATT Configurator)
Use this format if you prefer a terminal-based build process while still leveraging Studio’s powerful configuration and code generation tools.
Visual Studio Code: This option sets up the project for development in Visual Studio Code, while still using Simplicity Studio for initial configuration and code generation.
The project includes:
A Simplicity Studio .slcp file for managing software components and peripheral settings
Configuration files for building and debugging in VS Code (tasks.json, launch.json, etc.)
Full support for Advanced Configurators (Pintool, GATT Configurator, ZCL AP)
Use this format if you want to do all source code editing, building, and debugging inside VS Code and keep using Simplicity Studio for software component updates and configuration. Refer to the Simplicity Studio VS Code User Guide for setup and usage details.
CMake: This option creates a CMake-based project along with a Simplicity Studio configuration file (.slcp). It is designed for developers who prefer using the CMake build system with GCC in command-line or external IDE environments.
The project includes:
CMake build files (CMakeLists.txt) compatible with standard CMake tools
A .slcp file for configuring software components and peripheral settings in Simplicity Studio
Support for Advanced Configurators (Pintool, GATT Configurator, ZCL AP)
Use this format if you want to build the project using CMake and external build tools or CI.
Select an option from the list and click Finish.
The Running Initial Project Configuration Tools generation message displays while your project is created.
When the project is created, it displays in the PROJECTS pane with the project SLCP displayed on a tab displaying information about the project and details on how to use and configure it.
