4 ms·
Until you need to build a cross-platform cmake-based project on windows. Which means modifying the system path using the lovely "environment variables" panel st
by Aeolos 11y ago
Until you need to build a cross-platform cmake-based project on windows. Which means modifying the system path using the lovely "environment variables" panel straight from the Win95 era, downloading and compiling dependencies (half of which fail to compile on MSVC due to lacking standards-compliance), dll hell and all the other MS cruft.
Contrast to apt-get install foo-dev or brew install foo on Linux and MacOS respectively.
- fsloth 11y ago"Contrast to apt-get install foo-dev or brew install foo on Linux and MacOS respectively." Having a project that builds painlessly on third party developer machines requires effort from the project and is not guaranteed automatically by the chosen platform. Apt-get also can fail if the dependency chain does not match exactly the configuration required by the project one wants to build. The best way to build software on windows is different, perhaps even less elegant, but claiming that Linux/OS X builds are automatically correct does not match my experience. Projects which have an incentive to provide a windows build usually can be built out of the box pretty painlessly, even with CMake. From my experience, the best indicator of a pain free build on a platform is the number of users the project has on the said platform, not the platform.
- pjmlp 11y agoNot much different than using most commercial UNIXes or embedded OSes actually.
- GFK_of_xmaspast 11y agoI'll agree that the path setup is regrettable, but I don't remember any other serious build annoyances with cmake-on-windows.