search for: findconfigfile

I don't know anything about Interix. It may be best to defer a true Win32 port. It's not just the time it would take to do it, it's the time to keep it up to date as LLVM evolves. The Win32 port will constantly break, and I don't have the time to keep fixing it. I've got my own time-consuming projects :) That said, the architectural issues should still be addressed. What

...uld* keep the configuration files for llvmc and anything else that uses configuration files in that directory. However, the likely place for these would be the llvm installation directory. I might drop the notion of "special paths" in the sys::Path interface and just replace it with "FindConfigFile" which would do the right thing on a given platform. > How will it handle the Windows custom of having spaces in file > and directory names? (GNU make hates it.) I think this is where we use cygwin which has already been shown to work with our makefiles. > Why would it need to kn...

Jeff, These are all reasons why the Win32 port doesn't exist today. LLVM is heavily influenced and implemented by Unix tools/concepts/facilities. Since building on Win32 will also be a problem, I think that we should just target cygwin as our Win32 solution for now and get that to work really well. I know cygwin is a slow pig, but at least we can get LLVM to work with it. We also have Interix