Jed Brown

The environment variable `GIT_FAT_VERSION` is referring to the format of the placeholders for fat files. It exists for debugging/testing purposes, not for general use. Duane Murphy [email protected] writes: > We...

It looks like explorer will just need a build script similar to this and then a flag to activate it. https://github.com/EnzymeAD/enzyme-explorer/blob/main/builder/build-enzyme.sh A good task once the rebase is ready, in...

I agree with the sentiment, though it'll be common enough for people to define `ENZYME_DIR` or `ENZYME_LIB` for their build systems.

Here's an example doing that. The user sets `ENZYME_LIB=/path/to/ClangEnzyme-17.so` to activate Enzyme, which is otherwise optional. When I merge Rust support to this repository, it will still be able to...

There's an argument that it was a mistake that make variables set on the command line to be exported by default, but that bird has flown.

The build fails (or finds a system libLLVM) when the CMake files are missing for Rust's libLLVM. There is some upstream resistance to bundling those files in all contexts in...

Well, in standard mode, precompiled `libLLVMEnzyme-17.so` will be shipped in their binary distribution so the CMake files (and a C/C++ compiler for that matter) won't be needed. It is useful...

I like the intent, but note that many projects (especially the large/more mature ones) have their own taxonomy, labeling conventions, and issue templates. It feels out of our lane to...

Refresh in a running process is interesting, but I think a different use case. Suppose I have some user code (written in C or Fortran) that is failing and I...

It would be wonderful to hook these tests up to GitHub actions (or other continuous integration).