zephyr/arch/riscv/CMakeLists.txt

# SPDX-License-Identifier: Apache-2.0

add_subdirectory(core)

if(CONFIG_64BIT)
set_property(GLOBAL PROPERTY PROPERTY_OUTPUT_FORMAT elf64-littleriscv)
else()
set_property(GLOBAL PROPERTY PROPERTY_OUTPUT_FORMAT elf32-littleriscv)
endif()
license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-04-06 21:08:09 +08:00			`# SPDX-License-Identifier: Apache-2.0`

Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no> 2017-10-27 21:43:34 +08:00			`add_subdirectory(core)`

riscv: toolchain arguments for a 64-bit build For now we enforce the medany code model for 64-bit builds as we get reloc issues otherwise. The instruction set and ABI are also set to soft-float usage. The ilp32 ABI is explicitly specified on 32-bit build to make sure it is not using a wrong default if the same toolchain is used for both 32- and 64-bit builds. The archittecture options are the same as the SDK's riscv32 toolchain default in that case. Signed-off-by: Nicolas Pitre <npitre@baylibre.com> 2019-07-26 11:04:17 +08:00			`if(CONFIG_64BIT)`
			`set_property(GLOBAL PROPERTY PROPERTY_OUTPUT_FORMAT elf64-littleriscv)`
			`else()`
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no> 2017-10-27 21:43:34 +08:00			`set_property(GLOBAL PROPERTY PROPERTY_OUTPUT_FORMAT elf32-littleriscv)`
riscv: toolchain arguments for a 64-bit build For now we enforce the medany code model for 64-bit builds as we get reloc issues otherwise. The instruction set and ABI are also set to soft-float usage. The ilp32 ABI is explicitly specified on 32-bit build to make sure it is not using a wrong default if the same toolchain is used for both 32- and 64-bit builds. The archittecture options are the same as the SDK's riscv32 toolchain default in that case. Signed-off-by: Nicolas Pitre <npitre@baylibre.com> 2019-07-26 11:04:17 +08:00			`endif()`