dzhidzhoev wrote: > > > What exactly does it help with? Given that you're canonicalizing to a > > > forward slash, does that mean that some of the tools you use don't accept > > > backslashes (perhaps because they come from cygwin or the like)? > > > > > > As far as I understand, MinGW make, on which Chocolatey build is based, > > prefers \ or / slashes. > > I don't understand this sentence. Are you saying it prefers forward slashes > or backward slashes (or uniform slashes)? > > > Also, some include/library paths passed to clang seem to be > > ignored/incorrectly processed, when they have mixed path separators like > > C:....\foo/bar > > This is interesting. I'm surprised that errors are coming from llvm tools, as > the llvm path libraries treat forward and backward slashes (on windows) as > equivalent at a very low level. Could you try to reduce this to to figure out > which specific slash in the command is causing the error? I want to make sure > we're not working around a bug here...
When we were setting up cross-platform build and testing config, we had a multi-screen list of errors we had to solve. Also, we were unsure about the environment in which we would run this. Therefore we decided to bulk normalize all paths and some flags. But now I see that reverting this path separator-reverting change doesn't make much difference for us, so I revoked this part of the commit for now. https://github.com/llvm/llvm-project/pull/99266 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
