Mosè Giordano
Mosè Giordano
Tested only on 64-bit win
We've seen libraries with runpath settings like ``` 0x000000000000001d (RUNPATH) Library runpath: [/opt/x86_64-linux-gnu/x86_64-linux-gnu/sys-root/usr/local/lib:$ORIGIN] ``` We should prune `/opt` directories from runpath, as we already do for `/workspace`. Look at #1186...
Currently the wizard automatically detects only executable binaries and shared libraries as products in standard directories, anything else is ignored. In particular, there is no way to specify a `FileProduct`,...
We can't list both `libgcc_s.1.dylib` and `libgcc_s.1.1.dylib` as products because they have the same basename ```julia julia> Base.BinaryPlatforms.parse_dl_name_version("libgcc_s.1.dylib", "macos") ("libgcc_s", v"1.0.0") julia> Base.BinaryPlatforms.parse_dl_name_version("libgcc_s.1.1.dylib", "macos") ("libgcc_s", v"1.1.0") ``` This also means...
I'm honestly not sure this is really possible since it doesn't involve dispatch on new datatypes, but I feel like it'd be nicer if `code_typed(err; interactive=true)` would work out without...