You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the cxx build process it makes a recursive symlink to the crate root:
~ ls -l /Users/timh/workspace/libxyz/crates/core_logic/target/debug/build/core_logic-2813b45ab0a66cc3/out/cxxbridge/crate/core_logic/target/debug/build/core_logic-2813b45ab0a66cc3/out/cxxbridge/crate/
total 0
lrwxr-xr-x 1 timh staff 69 24 Feb 13:24 core_logic -> /Users/timh/workspace/libxyz/crates/core_logic
It would be good if that could be avoided - lots of code just blindly walks trees following symlinks to infinity. It's their fault but it's still annoying (example).
Also I assume there is some alternative that doesn't involve symlinks otherwise how does this crate work on Windows?
It would be nice if this symlink didn't exist.
The text was updated successfully, but these errors were encountered:
Ditto. Just ran into this issue with a C# project where Visual Studio walks the tree forever and throws an exception on solution build. This effectively makes the build.rs approach unfeasible for me. I can get around by killing the symlink as a post cargo build step, but eh...
In the cxx build process it makes a recursive symlink to the crate root:
It would be good if that could be avoided - lots of code just blindly walks trees following symlinks to infinity. It's their fault but it's still annoying (example).
Also I assume there is some alternative that doesn't involve symlinks otherwise how does this crate work on Windows?
It would be nice if this symlink didn't exist.
The text was updated successfully, but these errors were encountered: