3 ms·
To clarify your confusion in "provide binaries for clion": That does not make sense. You don't need binaries for CLion. If anything, you need binaries for GCC
by albertzeyer 12y ago
To clarify your confusion in "provide binaries for clion":
That does not make sense. You don't need binaries for CLion. If anything, you need binaries for GCC or Clang (the compiler - not the editor/IDE).
In case of a C library, the library binaries build with any compiler will work with any other compiler in your C/C++ project.
In case of a C++ library, you might need to have the library binaries build with the same compiler. So, as CLion uses GCC, you need library binaries which were also build with GCC. You can build the library with whatever build system you like (Xcode, CMake, by hand, automake, ...) as long as you use GCC.
In any case, it does not matter what editor/IDE (Vim, Xcode, CLion) and what build system (Xcode, CMake, ...) you use, it only matters, what compiler (GCC, Clang) you use.
- jokoon 12y ago> In any case, it does not matter what editor/IDE (Vim, Xcode, CLion) and what build system (Xcode, CMake, ...) you use, it only matters, what compiler (GCC, Clang) you use. so if I use clion on mac, do I give it frameworks or .dylib ?
- albertzeyer 12y agoBoth will work, as long as they were compiled with GCC or only provide a C/ObjC API if you want to use GCC in CLion.
- jokoon 12y agowith clang too ?
- albertzeyer 12y agoYea, for Clang, the libraries have to be compiled with Clang and you must use Clang in CLion.