This might help you if something doesn’t work, and anyway it’s a good way to learn. Setting CMAKE_VERBOSE_MAKEFILE to ON means that CLion will show you the commands that it is using to build your project. You might be able to slip -std=c99 in there but I didn’t check that it would appear in the right place. You might consider also adding -Wextra and -pedantic. Using add_compile_options adds the required compiler options for CSC173. I can’t find a way to change that, but they’re pretty close anyway ( Language Standards Supported by GCC). I noticed that this setting actually resulted in the -std=gnu99 option being used rather than c99.

Setting CMAKE_C_STANDARD_REQUIRED to ON means CLion will tell you if your compiler can’t do that rather than fall back on something else. When you create a C project, CLion will create a file named “ CMakeLists.txt” for you, as well as an initial source file (“ main.c”).Īssuming that you selected the C99 standard when you created the project, CMakeLists.txt should contain the following line already: set(CMAKE_C_STANDARD 99)Īdd the following to CMakeLists.txt: set(CMAKE_C_STANDARD_REQUIRED ON) Unfortunately I can’t figure out how to “export” a project so that it includes the source files and things like compiler settings, but without all the derived and without any hard-coded pathnames.īut I can tell you how to set the required compiler options for CSC173, and how to change the name of the executable program built by the project in case you want to do that. It is a commercial product, but there’s a 30-day free trial and special offers for students, educators, and others.

It is available for macOS, Windows, and Linux.

Using CLion for C (in CSC173) Using CLion for C (in CSC173) George Ferguson Last update: Summer 2021Ĭreative Commons Attribution-ShareAlike 4.0 International LicenseĬLion looks like a nice IDE from a company with a strong history ( IntelliJ IDEA, for example).

Clion makefile for windows