Using local makefile for CLion instead of CMake

Question

Is there a way to configure CLion to use a local makefile to compile code  rather than CMake  I can t seem to find the way to do it from the build options

User · Answer

Newest version has better support literally for any generated Makefiles, through the compiledb

Three steps:

install compiledb
```
pip install compiledb
```
run a dry make
```
compiledb -n make 
```
(do the autogen, configure if needed)
there will be a compile_commands.json file generated open the project and you will see CLion will load info from the json file. If you your CLion still try to find CMakeLists.txt and cannot read compile_commands.json, try to remove the entire folder, re-download the source files, and redo step 1,2,3

Orignal post: Working with Makefiles in CLion using Compilation DB

User · Answer

While this is one of the most voted feature requests  there is one plugin available  by Victor Kropp  that adds support to makefiles   Makefile support plugin for IntelliJ IDEA  Install  You can install directly from the official repository   Settings   Plugins   search for makefile   Search in repositories   Install   Restart  Use  There are at least three different ways to run    Right click on a makefile and select Run Have the makefile open in the editor  put the cursor over one target  anywhere on the line   hit alt   enter  then select make target Hit ctrl cmd   shift   F10 on a target  although this one didn t work for me on a mac     It opens a pane named Run  target with the output

User · Answer

I am not very familiar with CMake and could not use Mondkin s solution directly   Here is what I came up with in my CMakeLists txt using the latest version of CLion  1 2 4  and MinGW on Windows  I guess you will just need to replace all      g   mytest cpp -o bin mytest by make if you are not using the same setup    cmake minimum required VERSION 3 3  project mytest   set CMAKE CXX FLAGS    CMAKE CXX FLAGS  -std c  11    add custom target mytest ALL COMMAND mingw32-make WORKING DIRECTORY   CMAKE CURRENT SOURCE DIR     And the custom Makefile is like this  it is located at the root of my project and generates the executable in a bin directory    all      g   mytest cpp -o bin mytest   I am able to build the executable and errors in the log window are clickable   Hints in the IDE are quite limited through  which is a big limitation compared to pure CMake projects

User · Answer

Currently  only CMake is supported by CLion  Others build systems will be added in the future  but currently  you can only use CMake   An importer tool has been implemented to help you to use CMake   Edit   Source   http   blog jetbrains com clion 2014 09 clion-answers-frequently-asked-questions

User · Answer

Update  If you are using CLion 2020 2  then it already supports Makefiles  If you are using an older version  read on   Even though currently only CMake is supported  you can instruct CMake to call make with your custom Makefile  Edit your CMakeLists txt adding one of these two commands   add custom target add custom command  When you tell CLion to run your program  it will try to find an executable with the same name of the target in the directory pointed by PROJECT BINARY DIR  So as long as your make generates the file where CLion expects  there will be no problem  Here is a working example  Tell CLion to pass its   PROJECT BINARY DIR  to make This is the sample CMakeLists txt  cmake minimum required VERSION 2 8 4  project mytest   set CMAKE CXX FLAGS  quot   CMAKE CXX FLAGS  -std c  11 quot    add custom target mytest COMMAND make -C   mytest SOURCE DIR                           CLION EXE DIR   PROJECT BINARY DIR    Tell make to generate the executable in CLion s directory This is the sample Makefile  all      echo Compiling   CLION EXE DIR             g   mytest cpp -o   CLION EXE DIR  mytest  That is all  you may also want to change your program s working directory so it executes as it is when you run make from inside your directory  For this edit  Run - gt  Edit Configurations     - gt  mytest - gt  Working directory

User · Answer

To totally avoid using CMAKE  you can simply    Build your project as you normally with Make through the terminal  Change your CLion configurations  go to  in top bar    Run - gt  Edit Configurations - gt  yourProjectFolder Change the Executable to the one generated with Make Change the Working directory to the folder holding your executable  if needed  Remove the Build task in the Before launch Activate tool window box   And you re all set  You can now use the debug button after your manual build

[makefile] Using local makefile for CLion instead of CMake

Examples related to makefile

Examples related to clion