Build failure on the main branch

[maekawatoshiki]

Hello.

Following the setup guide in the README, I ran into the error below.
Would you be able to provide a CI workflow (similar to the one in the legacy branch) or a Dockerfile that reproduces the expected environment?

$ uv sync
$ source .venv/bin/activate
$ ./build.sh
[WARNING] MLIR Python modules may not be built. Consider running:
  cd /home/maekawa/work/lython/third_party/llvm-project/build && cmake --build . --target MLIRPythonModules
Using Python: /home/maekawa/work/lython/.venv/bin/python
Using MLIR from: /home/maekawa/work/lython/third_party/llvm-project/build
Configuring Lython with CMake...
-- The CXX compiler identification is GNU 13.3.0
-- The C compiler identification is GNU 13.3.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
CMake Error at CMakeLists.txt:16 (find_package):
  Could not find a package configuration file provided by "MLIR" with any of
  the following names:

    MLIRConfig.cmake
    mlir-config.cmake

  Add the installation prefix of "MLIR" to CMAKE_PREFIX_PATH or set
  "MLIR_DIR" to a directory containing one of the above files.  If "MLIR"
  provides a separate development package or SDK, be sure it has been
  installed.


-- Configuring incomplete, errors occurred!

[t3tra-dev]

I apologize, there was an omission in the README guide.
You actually need git clone --recurse-submodules, and then run ./build.sh after attempting ./build_mlir.sh and it should build successfully (this takes a considerable amount of time to clone & build LLVM locally).
I will address the CI workflow and Dockerfile later! Thank you.

[t3tra-dev]

I implemented the CI workflow in #34 and also fixed several build mechanisms!

If this is okay, I will close this / please close this.

[maekawatoshiki]

Thank you for the quick update! I've successfully built lython.

I have a question. Is there a specific reason why pybind11 and nanobind are managed via pip, not uv (in the CI)?

[t3tra-dev]

This build system looks for pybind11 and nanobind installed globally, so as a safeguard, we install those dependencies globally using pip in the CI environment.
Normally, if you are building locally, it should be fine if you have them installed via a package manager like brew.

I'm not entirely sure about the behavior around here, so it might be changed later, but...

[maekawatoshiki]

That makes sense.
I just thought it would be simpler to manage everything with uv for consistency.

Thank you for clarifying.