Using biicode and clion?
By : user3135641
Date : March 29 2020, 07:55 AM
To fix the issue you can do Currently it is not possible. Unfortunately both biicode and CLion use cmake and use different conventions about the project layout/structure, and at the moment they are simply incompatible. The good news are that the people at CLion are helping a lot to figure out the best solution so hopefully this will be fixed soon.
|
Can I use biicode for C++ on ubuntu 14.04 with Cmake 2.8.12.2?
By : user3147994
Date : March 29 2020, 07:55 AM
Hope this helps No, biicode requires cmake > 3.0. There is a setup command that helps installing it:
|
Use SQLite with biicode
By : user3215468
Date : March 29 2020, 07:55 AM
Hope that helps There're several problems. You just wrote in [includes] section sqlite.h instead of sqlite3.h and you should only write the prefix, sqlite/sqlite/sqlite3, later instead of the full dependency name. Then, you can solve it so: code :
[requirements]
sqlite/sqlite: 9
[includes]
sqlite3.h: sqlite/sqlite/sqlite3
[requirements]
fenix/sqlite: 0
[includes]
sqlite3.h: fenix/sqlite
|
Chaiscript #include statement mapping in biicode.conf
By : wmandai
Date : March 29 2020, 07:55 AM
this one helps. I want to create a biicode block that depends on the chaiscript block (lefticus/ChaiScript). If I include the chaiscript headers this way , You were doing well but you need to write the requirement too: code :
[requirements]
lefticus/ChaiScript: 1
[includes]
chaiscript/*.hpp: lefticus/ChaiScript
#include "chaiscript/chaiscript.hpp"
|
Specify output name in biicode
By : goroll
Date : March 29 2020, 07:55 AM
seems to work fine The auto-root-block: True behavior works as follows: If there is inside the project root a biicode.conf corresponding to the main project block, with a [parent] section, then, the block name will be taken from it. If there is no biicode.conf with parent, then the block name will be automatically defined from the current user and the project folder name. Changing either of them, should rename the block. code :
$ bii user myusername
ADD_BIICODE_TARGETS()
SET_TARGET_PROPERTIES(${BII_main_TARGET} PROPERTIES OUTPUT_NAME testsdl2)
|