Elliot Saba
Elliot Saba
Ah, I see. Yes, this is a problem. We expect to be able to `dlopen()` libLLVM.
.....okay _now_ you can show me how to transfer issues. *EDIT*: Aha! Figured it out.
It.... is indeed possible that we could integrate `Clang.jl` to do this. It's something that will have to go onto the wishlist for now; `Clang.jl` isn't that easy to use,...
We can build `clang` for windows and ship it with our BinaryBuilder so that users can opt into it with `CC=clang`.
We now ship a bevvy of compilers; you can opt-in to `clang` at any time, so I'm going to close this as fixed.
@xianwenchen Thanks for reporting this; I'm going to start from the beginning to help you figure out what's going on. First off, I'm not certain this is due to a...
How about we combine this with `--deploy`? We can have `--deploy=/absolute/path/to/directory` deploy the code into that directory instead of using `Pkg.devdir()` automatically. We can disambiguate the `user/repo` case from this...
No, no reason not to use a temporary directory. I think the reason it used the `dev` directory by default is defunct now; there were some kind of efficiency concerns...
> Is `--output-bin` the `products/` directory? Yes, my proposal is that `--output=` is equivalent to `--output-jll=/$(name)_jll.jl --output-bin=/products`. > is there also a step where the artifacts get copied from `products/`...
..........huh. Can you send me the file `libhidapi-0.dll`?