[Poyeyo]

Compiling what? May be some of us can help you.

If it's C++, I did learn cmake, and now I use the same script for Ubuntu and for Win7/VS2008 and Win8.1/VS2012, and so far I just don't care about compilation issues anymore. Sadly the VS site only has VS2015 now.

But yes, the first time you have to check the VS version and add all the proper env vars for the cmake scripts to find the libraries.

But anyway, it is much better than when I used mingw and made makefiles by hand.

[semi-extrinsic]

How about code written in C11? Or Fortran 95? Throw in a couple of numerical libraries you want to link to, maybe CUDA or some MPI or an optimized BLAS/LAPACK, and it's an all night party.

I lurk on a few sci.comp mailing lists, and the number and nature of problems that the Windows people have with compiling is crazy compared to Linux where the OS actually has a package manager and stuff Just Works.

As for cmake, I don't think it's any better than (gnu)make. I've seen big projects with complex buildsystems (eg. PETSc from Argonne) switch to cmake and then switch back again to make quite quickly. A frequent "problem" with make, I think, is that people learn just enough about makefiles to compile HelloWorld.cpp and then use that knowledge for everything.

[Poyeyo]

I think I agree with you on all fronts, simply because the online cmake documentation is not as good as it should be.

For BLAS, it has a

    find_package ( BLAS )

script, which you can use. The same for CUDA. They define cmake variables you can use later for the include and link search paths.

https://cmake.org/cmake/help/v3.0/module/FindBLAS.html

https://cmake.org/cmake/help/v3.0/module/FindCUDA.html

I haven't used C11 or Fortran95, only C++11, and I had to add a cmake script for it, you can find it as CheckCXXCompilerFlag somewhere in the web.

I have to use Visual Studio instead of mingw because I'm using some winSDK libs, and VS has no (gnu)make, and what VS offers for the command line is not cross-platform, making it a poor investment of my time to learn about it.

After climbing just a section of the the steep cmake learning curve, I have deleted the solution and project files from my repository, and now I use cmake to compile and run the project in the command line with both VS2008 in Win7 (the PC) and VS2012 in Win8.1 (the laptop), without any path dependency. Previously the solution files depended on both my username and the path, and just moving the folder was cumbersome and required a lot of fiddling with those files.

Another thing I really like is the concept of an out of source build, and that's very easy to set up and use with cmake.

I now can write

    git clone somewhere:my_project.git
    cd my_project
    mkdir build && cd build
    cmake -DCMAKE_INSTALL_PREFIX:PATH=../install ..
    cmake --build . --target install && cmake --build . --target run

in both Ubuntu and Windows and see my program running, which means I will not go back to make, or nmake or gmake anytime soon.

[k__]

Native modules for Node.js for example.

[pzone]

Doesn't help the slow-as-molasses NTFS unfortunately, or the inefficient scheduler.