
In the simplest use, this tool is used like this compiledb -n make. This is built from a python tool called compiledb. The CMakeLists file is one of two 'databases' you can make for CLion to describe the contents of a C++ project - the other is a compiledb json file. It should look 'good' in the sense that there are not many false positive error flags. Regardless of my parenthetical comments, you should see something like this:ĭrive around in the source panel and open some code. It may be that we need to add some extra directories to it for things like the libxml2 and curl headers).
#Cmakelists.txt not found clion code
Once this process completes, you should get a CMakeLists.txt file that is pretty comprehensive (AFAIK, this cannot be used to build code without some additions, but it serves as a database for CLion. The end result will take a few seconds to load and will show messages at the bottom of the screen regarding various scanning and indexing operations. For Hyrax, that means the $prefix/build/deps/include and $prefix/build/include directories. In the later case, code all the dirs with headers you want to be found. looking for code to be compiled and also, in the lower panel, for headers to be included. CLion will scan the selected directories. Use this dialog to choose which directories to scan.


When you start CLion, you will see a dialog boxĬlick on the New CMake Project from Sources and you will see the following Or, you've done something else to get our server code.Have used the script(s) to checkout the three C++ projects 'hyrax-dependencies,' 'libdap4,' 'bes.'.Checkout the hyrax git repo from GitHub ( ) and.3.2 Setting up Custom Build Applicationsįirst, you need to decide if you want to work with all of the C++ code as one 'project' or use a separate project for each of 'hyrax-dependencies,' 'libdap4,' and 'bes.' In practice, you choose one way and then switch without paying too great a penalty.įor the rest of this HowTo, I'll assume you have done the following:.
