IDE Configuration Tab (DATAFLOW Frames)
This Reference Article has been written for Version 2.1 of the DATAFLOW Software. For Previous Releases use the version selection in the navigation bar at the top of this page.
This Tab is part of Toolchain Configuration Page in the Project Settings dialog.
Tab Description
The IDE Tab in the Toolchain Configuration Page is used to configure IDE specific settings for a Build Toolchain. The settings depend on the type of Toolchain.
IAR Workbench for ARM
| Workspace Location |
This field defines the path for the generated IDE configuration files. This must not overlap with any other toolchain in the project. |
| Create Subdirectory per Project | When this field is checked, each project inside the generated IDE workspace/solution will be placed in its own sub folder. |
| Workspace Name |
The name of the generated IDE workspace/solution. When this field is empty, the name of the Build Configuration is used instead. |
The location and name of the IAR workspace can be configured independent from the generated source code. It is possible to place all IAR files in a single folder or to create a subfolder for the project inside the generated IAR workspace.
All generated source code file will be referenced using relative paths.
The Workspace name is the name of the root component the build configuration has been attached to. If a name is entered in the field, this name will be used instead.
Microsoft Visual Studio
| Solution Location |
This field defines the path for the generated IDE configuration files. This must not overlap with any other toolchain in the project. |
| Create Subdirectory per Project | When this field is checked, each project inside the generated IDE workspace/solution will be placed in its own sub folder. |
| Solution Name |
The name of the generated IDE workspace/solution. When this field is empty, the name of the Build Configuration is used instead. |
| Windows SDK |
For Windows based builds, the Windows SDK must be configured. The developer must ensure that this SDK is available, otherwise building the generated solution will not be possible. |
The location and name of the Visual Studio Solution can be configured independent from the generated source code. It is possible to place all Visual Studio files in a single folder or to create a subfolders for the projects inside the generated solution.
All generated source code file will be referenced using relative paths.
The Solution name is the name of the root component the build configuration has been attached to. If a name is entered in the field, this name will be used instead.
The Windows SDK version used in the generated visual studio project can be configured as string.
GNU Makefile
| Makefile Location |
This field defines the path for the generated IDE configuration files. This must not overlap with any other toolchain in the project. |
| Create Subdirectory per Project |
When this field is checked, each project inside the generated IDE workspace/solution will be placed in its own sub folder. |
| Makefile Name |
The name of the generated IDE workspace/solution. When this field is empty, the name of the Build Configuration is used instead. |
The location and name of the GNU Makefile can be configured independent from the generated source code. It is possible to place all Makefiles in a single folder or to create a subfolders for nested Makefiles (if any).
All generated source code file will be referenced using relative paths.
The Makefile name is 'Makefile' by default. If a name is entered in the field, this name will be used instead.
No IDE (Config Header Generator)
| Config Header Location |
For a Non IDE Toolchain the path to the folder the configuration files will be generated is configured. Note: The Headers will be placed in a sub folder called 'Config' at the given path. This matches the behavior of the other toolchains, where the config files are always in a sub folder relative to the workspace/solution location. |
For the 'No IDE' toolchain, only Configuration Headers for Imt.Base libraries are generated. The path where these header files will be located can be configured.
Tab Actions
This tab does not provide any special actions.
Required Module: DATAFLOW Frames
This Article has been written based on V2.1.1 of the DATAFLOW software.
Latest update 2023-05-31 by WUM.
Comments
0 comments
Please sign in to leave a comment.