Could you release binding for v18.1.8 ?

[Kakadu]

I tried to do this myself but after ./setup.sh llvm-config-18 and dune b --profile=release I got an error. No idea how to proceed @alan-j-hu

➜  llvm-dune git:(v18.1.8) ✗ dune b --profile=release                                              
File "src/target/static/dune", line 8, characters 9-21:
8 |   (names target_ocaml)
             ^^^^^^^^^^^^
target_ocaml.c:18:10: fatal error: target_ocaml.h: No such file or directory
   18 | #include "target_ocaml.h"
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
File "src/target/shared/dune", line 8, characters 9-21:
8 |   (names target_ocaml)
             ^^^^^^^^^^^^
target_ocaml.c:18:10: fatal error: target_ocaml.h: No such file or directory
   18 | #include "target_ocaml.h"
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
➜  llvm-dune git:(v18.1.8) ✗ find . -iname target_ocaml.h                                                                                                    4.14.2+flambda
./_build/default/src/target/target_ocaml.h
./src/target/target_ocaml.h
./llvm-project/llvm/bindings/ocaml/target/target_ocaml.h

[alan-j-hu]

Sorry, I was trying to figure out how to do this after I released LLVM 17, but because of how some of the LLVM bindings source code is structured in LLVM 18, the Bash script has to be modified. IIRC this wasn't straightforward, and I need to take another look at it.

[lynzrand]

Hi, I'm trying to work on this in my fork, including refactoring setup.sh into a more maintainable setup.py. I will make a PR once it's working.

As of the problem in this issue, I found that adding the corresponding C include directories (-I../ in src/target/shared/dune; -I../../../target in src/transform/passbuilder/shared/dune) fixes build errors. I will try to reflect this in my fork.

[alan-j-hu]

Hi, I want to go back to the original packaging approach of building via LLVM's CMake build system. I have two PRs open for the next release at ocaml/opam-repository#27178 and ocaml/opam-source-archives#40.

However, the opam package repo maintainers have not interacted at all with my PRs. I figure it must be the holiday season and they must be resting, but if they don't respond in a while, I'll have to find a way to flag them down.

[Kakadu]

However, the opam package repo maintainers have not interacted at all with my PRs. I figure it must be the holiday season and they must be resting, but if they don't respond in a while, I'll have to find a way to flag them down.

Usually, I undraft the PR and write in the title 'READY FOR REVIEW'. @alan-j-hu