What could be improved is how the ASM-VASM files are setup, and adding VBCC as a C/C++ compiler variant. * CMake modules for VASM is preinstalled in the proper directory so enable_language(ASM-VASM) works without extra tinkering * using cmake, the m68k-amigaos.cmake toolchain file is preloaded and has all the required variables, so all you need to do is: mkdir build & cd build & cmake. CPU architecutre: Intel(R) Core(TM) i7-4790K CPU 4.00GHz CPU logical cores: 8 CPU physical cores: 4 CPU clock speed: 3.998 GHz CPU Hyper-Threading: enabled RAM total: 31.962 GiB RAM free: 21. * Aliases for m68k-amigaos-gcc to just gcc etc (so it's like how it would be when compiling directly on Amiga with a Makefile) * Environment variables set for CC, CXX, AR, LD, RANLIB etc, Create an untitled project, just to open CLion.
#Clion gcc install
Download and install MinGW to C:MinGW In MinGW, install: mingw32-base and mingw32-gcc-g++ Download and install CLion. The AVR toolchain can be downloaded from the Microchip site, and avrdude utility from Savannah. Download and install the official Arduino IDE (1.6.9). We’ll continue to use the Arduino libraries. My improvements are on all ends in the case of Docker: This will involve using the CLion IDE, the CMake build system, the GCC for AVR toolchain, and the avrdude flashing utility. My goal is to have an as much ready to go prebuilt environment for people to use with whichever Amiga flavor they want. My goal was to ideally have only a minimum of setup steps in a cmake project, which means that I want only use find_package() and everything else is automatically properly configured. Visit Jetbrains E-store to apply for academic license. During the setup, select the top directory of your MinGW installation and select your CMake executable. My toolchain works for me, but I wouldn't be surprised if there is a more elegant approach. Once the three libraries (GLEW, GLFW, and GLM) are installed, you should be able to compile your program using CLion.
0 kommentar(er)
