Building Boost.Python for versions before 1.80.0

[devm18426]

I'm currently trying and failing miserably to build Boost.Python for Boost version 1.74 on Windows.

I was able to do it on my local machine (after MUCH trial and error) but on Github Actions it just won't go.

I'd really appreciate any tips on what I should be doing.

Thanks in advance.

[devm18426]

I think I got it working.

Initially I tried to download/install Boost with this action and then run b2 for Boost.Python.

Unfortunately, it appears that the Boost archive provided by this Action doesn't have the Boost.Python sources in the top level boost directory:

From what I can tell, this causes b2 to try symlinking those files from the libs directory using the Windows mklink command, which fails. I can't understand why.

When looking at the official Boost source directory structure (downloaded from here for example), the boost directory contains everything (including the Boost.Python code):

I don't know how this Action's archives were generated so I can't explain why the structures are different, or why b2 causes issues.

So then I tried downloading the official ZIP and building from there and that did the trick.

[MarkusJx]

I've started a build for version 1.74.0, let's see how that'll play out. If the build doesn't fail, I'll probably just replace the windows binaries in order to prevent this action from breaking. This will lead to continuity errors but I'll deal with that probably never so it'll be fine.

I'll post an update once there is something to report

[MarkusJx]

Update: Didn't work, will try again later

[devm18426]

Markus, you're amazing. Thanks for the effort! Much appreciated. Hope you're able to work it out.

[MarkusJx]

I've uploaded a version of boost 1.74.0 for windows server 2019 and support for python 3.7, 3.8 and 3.9. Python 3.10 and up unfortunately don't work.

[devm18426]

That's great Markus, thanks so much.

Regarding 3.10, if you're interested, it's possible to very easily patch the code so it compiles. The issue stems from usage of a function in the Python API which became private in 3.10: _Py_fopen. In this change you may see how they fixed this issue in Boost.Python 1.76. Essentially changing the use of _Py_fopen with a standard fopen in a specific file, exec.cpp.

I can confirm that making this small change in 1.74 works just as well. You may see how easily I achieved this in Powershell with a simple find/replace prior to building:

(Get-Content libs\python\src\exec.cpp).replace('_Py_fopen', 'fopen') | Set-Content libs\python\src\exec.cpp

https://github.com/devm18426/stpyv8/actions/runs/5904217668/workflow#L115

That said, I haven't tried this trick with 3.11.

Thanks again