![]() # You may need to set BACKWARD_USE_BFD to 0 in its `hpp` and `cpp` files to avoid linker errors. # stack traces will still work, but won't show unmangled symbol names or source code snippets. The '-lbfd' dependency is optional, and if it is disabled, the # Link agains libbfd to ensure backward-cpp can extract additional information from the binary, My Utils/CMakeLists.txt therefore looks like this: SET(UTILS_HEADERS. This is to load a 3rd party instrument the old fashion way without using the quick load functionality. Drag an nki to the empty workspace pane on the right. I did this in order not to "pollute" the main CMakeLists.txt file with directives only pertaining to a small part of the project. Navigate to the folder that has your 3rd party kontakt libraries. In the interest of modularity, I have added the backward-cpp project as a dependency to the only project library which actually uses it, Utils. I have added a CMake dependency to one of these project libraries (it's the backward-cpp stacktrace prettifier). Many utilities are also contained in a separate Utils library. The main functionality of the project is contained inside an Engine library which is statically linked to the main executables using something like target_link_libraries(programX Engine). ├── CMakeLists.txt (this contains the main executable targets) The projects consists of several output executables, each having relatively little custom code, but leveraging a few common libraries: programX I am currently working on a C++ project using CMake as its build system.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |