arno/bddisasm
1
0
Fork 0
mirror of https://github.com/bitdefender/bddisasm.git synced 2024-12-23 06:28:13 +00:00
Code Issues Releases Wiki Activity

Use Release as the default build type

Browse Source
This commit is contained in:
Ionel-Cristinel ANICHITEI 2020-11-17 11:41:19 +02:00
parent 2eb472cdab
commit f5d91d7cb5
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CMakeLists.txt
View File

@ -9,8 +9,8 @@ project(bddisasm
) )
if (NOT CMAKE_BUILD_TYPE) if (NOT CMAKE_BUILD_TYPE)
message(STATUS "No build type given. Will use 'Debug'") message(STATUS "No build type given. Will use 'Release'")
set(CMAKE_BUILD_TYPE Debug) set(CMAKE_BUILD_TYPE Release)
endif () endif ()
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/bin/x64/${CMAKE_BUILD_TYPE}) set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_SOURCE_DIR}/bin/x64/${CMAKE_BUILD_TYPE})

2
README.md
View File

@ -74,6 +74,8 @@ make
make install make install
``` ```
The default build type is Release.
Note that the current install behavior differs based on how the installation is done. When using make, the `bdshemu.h` header is placed by default in `include/bddisasm/bdshemu` in your install location, while the cmake method will place it in `include/bddisasm`. Using cmake also provides support for pkg-config. Note that the current install behavior differs based on how the installation is done. When using make, the `bdshemu.h` header is placed by default in `include/bddisasm/bdshemu` in your install location, while the cmake method will place it in `include/bddisasm`. Using cmake also provides support for pkg-config.
### Building disasmtool_lix ### Building disasmtool_lix