Searched full:build (Results 1 – 21 of 21) sorted by relevance
3 This project uses CMake and the GNU ARM-Toolchain as build system and GDB/OpenOCD are used for debu…6 It allows to build the project either by using a command line terminal or by using IDE's like [VSCo…44 # Commandline build instructions50 2. Create a directory named 'build'52 `mkdir build`54 3. Go to the created `build` directory56 `cd build`212 2. The *`settings.json`* file under `.vscode` directory is the place where one can change the build…213 These are the build options that will be provided to CMake. 214 …Please see chapter [Commandline Build Instructions](#commandline-build-instructions) for informati…[all …]
128 $ mkdir build129 $ cd build158 $ mkdir build159 $ cd build273 * Click on "CMake: Debug: Ready" and select build type Debug or Release. 276 * Click on "Build" to build the project. 277 ![cmake build](doc/images/vscode-cmake-build.png)278 * Wait for build process to finish279 * Binary files will be available under `./build/src/apps/LoRaMac/`374 * Click on "CMake: Debug: Ready" and select build type Debug or Release. [all …]
4 build/
68 - Added I2C driver support for B-L072Z-LRWAN1 and Nucleo platforms to the build system389 - Added CMAKE build system support408 - Added CMAKE build system support
63 # Options for DEBUG build66 set(CMAKE_C_FLAGS_DEBUG "-Og -g -DDEBUG" CACHE INTERNAL "C Compiler options for debug build type")67 set(CMAKE_CXX_FLAGS_DEBUG "-Og -g -DDEBUG" CACHE INTERNAL "C++ Compiler options for debug build typ…68 set(CMAKE_ASM_FLAGS_DEBUG "-g" CACHE INTERNAL "ASM Compiler options for debug build type")69 set(CMAKE_EXE_LINKER_FLAGS_DEBUG "" CACHE INTERNAL "Linker options for debug build type")71 # Options for RELEASE build73 set(CMAKE_C_FLAGS_RELEASE "-Os" CACHE INTERNAL "C Compiler options for release build type")74 set(CMAKE_CXX_FLAGS_RELEASE "-Os" CACHE INTERNAL "C++ Compiler options for release build type")75 set(CMAKE_ASM_FLAGS_RELEASE "" CACHE INTERNAL "ASM Compiler options for release build type")76 set(CMAKE_EXE_LINKER_FLAGS_RELEASE "" CACHE INTERNAL "Linker options for release build type")
8 "program": "${workspaceRoot}/build/src/apps/@APPLICATION@/@TARGET_NAME@",20 { "text": "cd ${workspaceRoot}/build" },
33 # Object build options
32 # Object build options
63 # Build platform specific board implementation74 # Build platform specific board implementation95 # Build platform specific board implementation116 # Build platform specific board implementation137 # Build platform specific board implementation148 # Build platform specific board implementation159 # Build platform specific board implementation170 # Build platform specific board implementation181 # Build platform specific board implementation
44 // The build number does not refer to the component, but to the build number
3 build:
5 "compileCommands": "${workspaceRoot}/build/compile_commands.json",
48 // build a 16bit number in PAM7QGetGpsData()
83 // data : first flash line (64 bits). This variable must be updated after each build. in HardFault_Handler()
317 …uint32_t ContextQueue; /*!< Injected channel configuration context: build-up over …383 …figTypeDef InjectionConfig ; /*!< ADC injected channel configuration build-up structure */
2002 /** Build configuration from header macros. */
1779 /* Handle hadc saves the context under build up over each HAL_ADCEx_InjectedConfigChannel() in HAL_ADCEx_InjectedConfigChannel()
104 …* The library installer contains a project file to re build libraries on MDK-ARM Tool chain in the…121 …* Define macro ARM_MATH_BIG_ENDIAN to build the library for big endian targets. By default library…