Make package available for other than Linux

[proto3]

The packaging script only produce linux .so library for now, then it is included as a package resource.

I still need to figure out what is the most common solution to this problem. Cross compile multiple targets into the package, or give the package anything it needs to compile at installation.

[Thaddeus-Maximus]

Do you know how to do either of these solutions? I'd really be interested in using this on Windows but I'm completely aloof when it comes to compiling libraries for python.

[proto3]

I have found that python wheels is exactly what I was looking for. It can provide built version of the package (through .whl files) on some chosen platforms, but it also contains build instructions for the other platforms to be able to build the package anyway.

My problem now is about using cavaliercontours' static library (.so) plus a bit of python code with using ctypes to load it.
Using pybind11 instead would allow to build the package directly without external dependencies. Thus it would be easier to use Wheels like this.

I had a look at pybind11, but I have not much time to work on it currently.

[DorPractical]

I got it working on Windows by replacing the .so file with a DLL.
You need to compile the libcpp on the repository and than get the DLL and replace it in the file:
filename = "libCavalierContours.dll"

[Andrewwu98]

I got it working on Windows by replacing the .so file with a DLL. You need to compile the libcpp on the repository and than get the DLL and replace it in the file: filename = "libCavalierContours.dll"

I have tried it but still can't work. Could you please explain it with more details?

[IdoPractical]

I got it working on Windows by replacing the .so file with a DLL. You need to compile the libcpp on the repository and than get the DLL and replace it in the file: filename = "libCavalierContours.dll"

I have tried it but still can't work. Could you please explain it with more details?

Did you compile the libcpp and got a DLL file?