setuptools - where does python CMake Extension subdirectory build/lib.system name comes from?

Question

I'm trying to find out how the name/directory build/lib.system is chosen/created within a distutils(setuptools) python build process...

when i build dlib python module from source using python3 setup.py build i can see the following

build/
├── bdist.linux-aarch64
├── CMakeCache.txt
├── CMakeFiles
├── lib.linux-aarch64-3.8
└── temp.linux-aarch64-3.8```

reading at the official documentation in 4.1 says:

Depending on the system, the module file will end up in a subdirectory build/lib.system...

---

It's not clear to me where does lib.${system} comes from and if i can configure it using a class extension argument or it is a -DCMAKE_VARIABLE?

I'm using setuptools instead of distutils but for now it looks like the documentation in this subject is the same.

Please any help will be appreciated also, if anybody knows which is the path of the source code for class Extension will be very helpfull.

thanks!!

question from:https://stackoverflow.com/questions/65898022/where-does-python-cmake-extension-subdirectory-build-lib-system-name-comes-from

Answer 1

Waitting for answers