Yes, that is very true.
"tooling that can require a long and complex setup from an expert"
If one is on windows, one can 1. install visual studio community edition and 2. click "new project".
Sure, it's nowhere close to npm or Rusts's crates or go's dependency management but that's bit hyperbolic way to express it. I can waste hours trying to get Rusts' dependencies working if I'm using something bleeding edge.
Outside Windows, it's not so simple though. Most IDEs struggle with heavily templated code. For instance, I tried CLion for a while, but it completely runs into the ground when you use e.g. Armadillo (no completion, correct code is highlighted as incorrect).
I have spent a big part of my time trying to find that IDE developer experience back.
Nowadays Qt and KDevelop do a good job, but it wasn't always like that, specially in the mid-90's when we were already enjoying C++ Builder and Delphi on Windows.
Yes, this is the main reason I prefer visual studio :). I know my way around unixes but since I don't use them for my daily work I forget most of the things I would need to remember to be productive.
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.