I’m using Clion on OSX, and it works great.
I would like to use Clion also on windows, but there I have some issues making it work. I am probably missing some key components.
I have installed the latest version of clion.
I have added a Clion exporter in Projucer, but it is greyed out.
I have added a code::blocks exporter (as I read that this is where the clion exporter gets its settings)
I have Visual Studio installed, and working fine.
What else do I need? Is there a guide I can follow?
If you want to use the CLion exporter of Projucer on Windows, you need a port of gcc for Windows (commonly called “MinGW”). The easiest way to get it is to install the Code::Blocks IDE, which bundles that compiler. You can also get gcc for Windows (without installing the Code::Blocks IDE) from:
If you want to use CLion with the MSVC compiler (which comes with Visual Studio), you can’t use the CLion exporter of Projucer. You can try using FRUT (I’m the author), to convert your
.jucer project into a CMake project, and then open it in CLion. I don’t use CLion, so I can’t guarantee that it would work, but I’m happy to help (here, via PM, or on GitHub) if you get into issues.
I hope this helps!
Does anyone else find compilation using MinGW on Windows achingly slow? Any tips on improving compile times?
Thank you. I will try to go down the msvc road.
I use FRUT with CLion and I can only recommend this approach… much better than the projucer target in my opinion.
Can you please explain what’s easier/works better in the FRUT generated version compared to the Projucer CLion exporter?
I imagine because it can use the MSVC compiler instead of GCC… ?
At least last time I checked (I use CLion mostly on Mac), you couldn’t use the debugger with MSVC, so that option wasn’t very effective.
I had the same experience. However since Visual Studio supports CMake as an alternative project format, I loaded my CMake based projects directly in Visual Studio to do some windows debugging, which worked unexpectedly straightforward out of the box. However those were hand-written CMake files that I developed with CLion on MacOS and Linux, no Projucer generated CLion Projects
With FRUT, you can modify the build as you wish… add targets for test projects and what not. I’m taking advantage of this now while I’m building my first plugin, and I imagine it will become even more usefull when I start setting up CI/CD pipelines for various formats and platforms. With the projucer, any change you make will be overwritten.
I think the Projucer is a great starting point if you are new to audio development (like I was) but it doesn’t support professional software engineering practices.
I work mostly on a Mac and and I don’t think I have had the need to debug on Windows since I switched to FRUT. Loading the CMake file in Visual studio sounds like a good way to go though.