Can Clion use bcc (Borland C++ Compiler)?

You can specify the compiler in File | Settings | Toolchains or using CMake options. Find more details in our web-help: https://www.jetbrains.com/help/clion/how-to-switch-compilers-in-clion.html.

Thanks for the prompt response. Looking at Files | Settings | Toolchains, I can't seem to find a way to specify the path to the compiler. In the Environment drop down, can only select Cygwin, MinGW, MSVC or WSL. Is there a way to specify the compiler executable in CLion 2018.1?

Thanks,

J-F

You can specify the path to the desired compiler executable in the "C++ Compiler" field.

Thanks again for the reply.

I'm slowly muddling my way through. I set the compiler path, and that seemed to work but fails at getting compiler information:

"C:\Program Files\JetBrains\CLion 181.3263.17\bin\cmake\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug "-DCMAKE_C_COMPILER=C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe" "-DCMAKE_CXX_COMPILER=C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe" -G "Borland Makefiles" -G "CodeBlocks - MinGW Makefiles" C:\Users\jfbil\jfbilodeau@gmail.com\Projects\Experi\RadStudio
-- The C compiler identification is Embarcadero 7.30.36036
-- The CXX compiler identification is Embarcadero 7.30.36036
-- Check for working C compiler: C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe
-- Check for working C compiler: C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Embarcadero/Studio/19.0/bin/BCC32.exe -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/jfbil/jfbilodeau@gmail.com/Projects/Experi/RadStudio/cmake-build-debug

Cannot get compiler information:
 Compiler exited with error code 1: C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\BCC32.exe -xc++ -IC:/Users/jfbil/jfbilodeau@gmail.com/Projects/Experi/RadStudio/Include -tM -Od -v -fpch-preprocess -v -dD -E
  

Seems like CMake wants to pass GCC command line parameters instead of BCC. I've tried to pass -G "Borland Makefiles" to CMake, but seems like CLion insists on including -G "CodeBlocks - MinGW Makefiles".

Forgive my ignorance, but under Toolchains, in the Environment drop down, there are four predefined choices: MinGW, Cygwin, MSVC and WSL. Which should I choose?

CLion supports only GCC/GCC-based, Clang and MSVC compilers. Some unsupported compilers still can successfully work in CLion, but, unfortunately, it looks like the Borland compiler is not from those. I've created a feature request in our tracker: https://youtrack.jetbrains.com/issue/CPP-12033. Feel free to comment or upvote.

Thanks again for your help! I greatly appreciate you taking the time to open an issue on my behalf.

J-F

Yes I completely understand exactly ,the same thing your going through.
Just today. I was going over the very same situation. Just to get a cross compiler to work. Because Clion has an extremely great speed that we need.. It becomes invaluable.
I got the VisualStudio to pull through and got errors as well from 2015 saying the compiler us disfunct ,and it's not.
The specification should be a base run. Clion could implement that feature in the drop down menu ;-) that would br very nice.