-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathSTM32-for-VSCode.config.yaml
112 lines (91 loc) · 3.5 KB
/
STM32-for-VSCode.config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
# Configuration file for the STM32 for VSCode extension
# Arrays can be inputted in two ways. One is: [entry_1, entry_2, ..., entry_final]
# or by adding an indented list below the variable name e.g.:
# VARIABLE:
# - entry_1
# - entry_2
# The project name
target: acquisinator
# Can be C or C++
language: C
optimization: Og
# MCU settings
targetMCU: stm32f3x
cpu: cortex-m4 # type of cpu e.g. cortex-m4
fpu: fpv4-sp-d16 # Defines how floating points are defined. Can be left empty.
floatAbi: -mfloat-abi=hard
ldscript: STM32F334K8Ux_FLASH_shifted.ld # linker script
# Compiler definitions. The -D prefix for the compiler will be automatically added.
cDefinitions: []
cxxDefinitions: []
asDefinitions: []
# Compiler definition files. you can add a single files or an array of files for different definitions.
# The file is expected to have a definition each new line.
# This allows to include for example a .definition file which can be ignored in git and can contain
# This can be convenient for passing along secrets at compile time, or generating a file for per device setup.
cDefinitionsFile:
cxxDefinitionsFile:
asDefinitionsFile:
# Compiler flags
cFlags:
- -Wall
- -fdata-sections
- -ffunction-sections
cxxFlags: []
assemblyFlags:
- -Wall
- -fdata-sections
- -ffunction-sections
linkerFlags:
- -Wl,--print-memory-usage
# libraries to be included. The -l prefix to the library will be automatically added.
libraries:
- c
- m
# Library directories. Folders can be added here that contain custom libraries.
libraryDirectories: []
# Files or folders that will be excluded from compilation.
# Glob patterns (https://www.wikiwand.com/en/Glob_(programming)) can be used.
# Do mind that double stars are reserved in yaml
# these should be escaped with a: \ or the name should be in double quotes e.g. "**.test.**"
excludes:
- "**/Examples/**"
- "**/examples/**"
- "**/Example/**"
- "**/example/**"
- "**_template.*"
# Include directories (directories containing .h or .hpp files)
# If a CubeMX makefile is present it will automatically include the include directories from that makefile.
includeDirectories:
- Inc/**
- Core/Inc/**
- Src/**
- Core/Src/**
- Core/Lib/micro-libs/can-manager/inc
- Core/Lib/micro-libs/ring-buffer/**
- Core/Lib/can/**
# Files that should be included in the compilation.
# If a CubeMX makefile is present it will automatically include the c and cpp/cxx files from that makefile.
# Glob patterns (https://www.wikiwand.com/en/Glob_(programming)) can be used.
# Do mind that double stars are reserved in yaml
# these should be escaped with a: \ or the name should be in double quotes e.g. "HARDWARE_DRIVER*.c"
sourceFiles:
- Src/**
- Core/Src/**
- Core/Lib/micro-libs/can-manager/src/*.c
- Core/Lib/can/lib/**/*_network.c
- Core/Lib/can/lib/**/*_watchdog.c
# When no makefile is present it will show a warning pop-up.
# However when compilation without the CubeMX Makefile is desired, this can be turned of.
suppressMakefileWarning: false
# Custom makefile rules
# Here custom makefile rules can be added to the STM32Make.make file
# an example of how this can be used is commented out below.
customMakefileRules:
# - command: sayhello
# rule: echo "hello"
# dependsOn: $(BUILD_DIR)/$(TARGET).elf # can be left out
# Additional flags which will be used when invoking the make command
makeFlags:
# - -O # use this option when the output of make is mixed up only works for make version 4.0 and upwards
# - --silent # use this option to silence the output of the build