Compile and (manually) install PyRx for BCAD v25

[schoeller]

Thanks for PyRx.

In order to be able to test potential contributions (e.g. stubs), one must manually test before creating a pull request. Below is a walkthrough in order to document for others to use.

Requirements: MS W11, BCAD 25.0.3, x64 hardware

1. Install Python 3.12 (https://www.python.org/ftp/python/3.12.7/python-3.12.7-amd64.exe)

2. Install Visual Studio 2019 community edition including BuildingTools (v142)

3. Install Boost 1.8.5 for VC v142 (https://sourceforge.net/projects/boost/files/boost-binaries/1.85.0/boost_1_85_0-msvc-14.2-64.exe/download)

4. Install WxWidgets as per download provided and extract into C:\Program Files\wxWidgets-3.2.0

5. Install WxPython on the PowerShell using pip install wxpython

6. Install the BCAD SDK BRX25.1.05.0 (https://www.bricsys.com/en-eu/developer-resources)

7. Set environment variables as follows

ARX2025=C:\Program Files\Bricsys\BRXSDK\BRX25.1.05.0
WXWIN=c:\Program Files\wxWidgets-3.2.0
BOOST=C:\Program Files\Boost_1_85_0
Py312=C:\Users\Sebastian Schoeller\AppData\Local\Programs\Python\Python312
WXPYWIN=C:\Users\Sebastian Schoeller\AppData\Local\Programs\Python\Python312Lib\site-packages\wx
BRX25=C:\Program Files\Bricsys\BRXSDK\BRX25.1.05.0

9. Fetch source code for PyRx
10. Modify RxLoaderV25.0.vcxproj and PyRxV25.0.vcxproj and change strings

inc-$(PlatformName)
lib-$(PlatformName)

to

$(BRX25)\inc$(PlatformArchitecture)
$(BRX25)\lib$(PlatformArchitecture)

11. Open PyRx.sln in Visual Studio 2019 Community Edition
12. Compile debug manually PyRxV25.0 and RxLoaderV25.0

13. Load module using _APPLOAD from Bin-folder

GitHub\PyRx\Bin\PyRxV25.0\x64\Debug\PyRxV25.0.brx
GitHub\PyRx\Bin\PyRxV25.0\x64\Debug\RxLoaderV25.0.brx

One should receive a message similar to below

The stub file should thus be generated in

GitHub\PyRx\PyRxStubs

14. Copy PyBrxCv.pyi, PyRxV25.0.brx, RxLoaderV25.0.brx into the installation directory wherever required.

Best

Sebastian

05.11.2024: Changed VS to 2019
11.11.2024: Changed WXWIN-instructions; changed load order

[CEXT-Dan]

Item 4, $(WXWIN) as noted in BUILDENV.txt. I have provided a wxWidgets build here.
https://drive.google.com/file/d/1ukMDR7qCfgEnD62-frIuph73dr-POv_9/view?usp=sharing

the issue could be that when linking, the .LIB and .DLL names must match the target. The download is “wxmsw32u_core_vc14x_x64.dll”
whereas in AppData\Local\Programs\Python\Python312\Lib\site-packages\wx, its “wxmsw32u_core_vc140_x64.dll”

you can't jut rename the files, however, you can compile wxWidgets yourself, but you have to go through every project and change the .LIB and .DLL names to exactly match what’s in wxPython.
Not hard, just tedious

Another thing is, I see is you should be loading RxLoaderV25.0.brx in _APPLOAD and not PyRxV25.0.brx, unless you already have a path to wxPython

There’s a cool app here. https://github.com/lucasg/Dependencies, You can target PyRxV25.0 and see your actual dependencies

[schoeller]

@CEXT-Dan : works like a charmer. Thanks a ton.

[CEXT-Dan]

Just to add. From a development perspective, it may be best to uninstall the user package, and work from the solution directory. just load from PyRxGit\Bin
Reason, stub generator and tests are designed to work in the solution dir.
It’s kind of a pain switching back and forth though, I.e. you may have to change the stub path in vs code.
but it's easier than copying stubs back an forth

[CEXT-Dan]

... and if you want to debug the C++ code, it’s probably best to load/run from the solution dir
plus debug builds are much faster to compile :)