Basilisk (Python) not configuring in Windows

[irmakcavdar]

Hello everyone,

I am trying to build the Basilisk (2.20) in WIndows 10. I am using a virtual Python environment (with Python 3.7) as it was mentioned in the website for building in Windows. The Basilisk is now added to Python and it passes the C++ tests, when I run the ctest in dist3. However, the Python packages or basically the Python wrapper is not build correctly because the pytest fails. Does anyone encountered the same issue or have any idea how to solve it?

Below I attach the error that I get after running pytest in ../src folder. Basically the Python module packages are empty, and I think that's why it asks for a valid name (to point to non-empty files). I am suspecting it may be related to a mistake that occurs while running the CMakeList.txt file.

`============================= test session starts =============================
platform win32 -- Python 3.7.0, pytest-7.4.3, pluggy-1.2.0
rootdir: ...\basilisk\src
configfile: pytest.ini
collected 183 items / 251 errors

=================================== ERRORS ====================================
__ ERROR collecting architecture/messaging/_UnitTest/test_CMsgTimeWritten.py __
ImportError while importing test module 'C:\Users\IrmakCavdar\git\basilisk\src\architecture\messaging_UnitTest\test_CMsgTimeWritten.py'.
Hint: make sure your test modules/packages have valid Python names.
`

[irmakcavdar]

Hey, it is resolved. Just make sure that Swig is installed correctly and recognized by your terminal!

[wlopesdawn]

Unfortunately we couldn't trust the guide on the website fully. What worked for us additionally was to:

• Make sure CL, cmake, Swig is working correctly (recognized by terminal)
• Make sure to use Visual Studio 16 2019
• Make sure to install the c++ components in Visual Studio (required for cmake)
• Install conan 1.60.0 (the recommended version didn't work for us)
• Use Python 3.8 (Python 3.7 didn't seem to work for us)
• Double check if paths are correct

Only after checking all these steps, were we able to run Basilisk succesfully on Windows (10).