Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing Visual Studio for IDE but using CMake for cross platform configuration
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COwell, we use cmake and VS to develop. And after the shock (from my side when I joined the company one year ago) I like it way better to be forced to write down your cmakelist.txt. It makes you THINK about the structure of your project before you shoot into the blue (aka "rmt -> new file" ). So we do it around. Add files into cmakelist first and configure/generate the .sln files via cmake
      singulars
    2. COcmake is a project generation tool: you define your project and files and build settings in one place, then use cmake to generate your visual studio file, xcode project, unix makefiles - etc. While there are some methods for going in the opposite direction, it's not the recommended setup. Is there a specific reason you don't want to generate your visual studio project?
      singulars
    3. CO@hsmith I would like to go in the opposite direction because I find it more convenient to create all my files through VS and all around treat it like you would any other Windows project (while writing the code for cross platform), but at the end of the day having all your files in your folders with cmakelist.txt ready to be configured on any other platform. I want to go from VS->CMake->Linux Make. I want VS in there for the ease of use and quickly doing windows builds. That's the best way I can put it.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload