These are my findings with the first steps to compile lpython on Msys2 environments.
The environments I tested are the ucrt64 and the clang64 environment.
the version file is not created. Minor problem as it can be created manually.
One has to install clang-15 instead of clang, as llvm-18 is not yet supported. I guess llvm-16 supported as well, but there is no canonical way to install this version of the toolchain with pacman. Later on I recognized, that lfortran builds on Msys2 use clang-15 as well.
src/bin/lpython.cpp includes hardcoded paths which match a conda environment. Has to be adapted somehow. Maybe some environment variables could be introduced to allow user defined paths to Python, numpy headers at build time.
The install is spread all over multiple folders. I have no clue how to create a standalone lpython install. This would be great for Windows vanilla CPython usage.
lfortran has to be started from the src/bin folder; see 4. Is this documented somewhere other than in a github issue?
Is there a way to automate the type-hinting to python source code somehow?
There are some warning during the compile process. I want to test further before adding these to this issue.
These are my findings with the first steps to compile lpython on Msys2 environments.
The environments I tested are the
ucrt64and theclang64environment.versionfile is not created. Minor problem as it can be created manually.clang-15instead ofclang, asllvm-18is not yet supported. I guessllvm-16supported as well, but there is no canonical way to install this version of the toolchain with pacman. Later on I recognized, that lfortran builds on Msys2 useclang-15as well.src/bin/lpython.cppincludes hardcoded paths which match a conda environment. Has to be adapted somehow. Maybe some environment variables could be introduced to allow user defined paths to Python, numpy headers at build time.src/binfolder; see 4. Is this documented somewhere other than in a github issue?I guess there will be more to tell later.