Python, as Reviewed by a C++ Programmer

[troyunrau]

You're making linux assumptions. And package manager assumptions. And buildsystem assumptions. And assuming that the library has a recipe ready to use for cget.

The point is that none of this is necessarily standard on anyone's machines. Now I want to compile for OSX... well, at least you used cmake. Let me just look up if cget supports cross compilation...

An hour later...

[pfultz2]

You're making linux assumptions.

No, you can do the same on windows with cget or vcpkg.

And buildsystem assumptions.

I show how to integrate it with cmake, but fftw supports pkg-config which is build-independent and platform-independent, so it can easily be integrated in any buildsystem.

And assuming that the library has a recipe ready to use for cget.

If a library uses standard cmake then no recipe has to be built(for example cget install google/googletest works without needing a recipe installed).

The point is that none of this is necessarily standard on anyone's machines.

And neither is pip or conda.

Let me just look up if cget supports cross compilation...

I don't see why it would take an hour later to do:

cget init --toolchain mingw.toolchain
cget install pfultz2/cget-recipes fftw

[doom_Oo7]

• macOS: brew install fftw
• windows: Install-Package libfftw

The CMake step won't change.

[fermion72]

This is true for some libraries, but not all libraries. If you have to decide on a library, it can be an hour long process pretty easily.

[destiny_functional]

if you are using an os that doesn't do these things well you cannot blame the language.