SimplifyLibCalls.cpp is no longer part of Transforms\IPO and Transforms\Scalar\SimplifyCFG.cpp is renamed to SimplifyCFG.cpp or something to that effect ( I didn't look up the actual checkins ). Having fixed that, I still can't get through the build: Creating library C:\work\s\llvm\win32\\bin\Win32\Debug/opt.lib and object C:\work\s\llvm\win32\\bin\Win32\Debug/opt.exp 1>opt.obj : error LNK2019: unresolved external symbol "class llvm::FunctionPass * __cdecl llvm::createLibCallAliasAnalysisPass(class llvm::LibCallInfo *)" (?createLibCallAliasAnalysisPass at llvm@@YAPAVFunctionPass at 1@PAVLibCallInfo at 1@@Z) referenced in function "public: __thiscall `anonymous namespace'::ForcePassLinking::ForcePassLinking(void)" (??0ForcePassLinking@?A0xe41c907a@@QAE at XZ) 1>C:\work\s\llvm\win32\\bin\Win32\Debug/opt.exe : fatal error LNK1120: 1 unresolved externals It'd be fine for me to use RELEASE_22 tag, but since cfe doesn't have a matching tag, this doesn't quite work. I tried checking out cfe of the same date as RELEASE_22 tag and got errors of clang mismatching llvm header files. I realize that msvs build is not of high priority but whoever shuffles the files around and changes the makefiles, at least have a decency to do the matching changes in the msvs project files.
Dmitri Makarov <nebraskin at yahoo.com> writes: [snip]> I realize that msvs build is not of high priority but whoever shuffles > the files around and changes the makefiles, at least have a decency to > do the matching changes in the msvs project files.Is it reasonable to ask this to people who doesn't know the format of MSVS project files? Furthermore, people are supposed to manage those XML project files with the MSVS IDE. IMHO, the only way to keep MSVC build up to date is to monitor the commits mailing list watching for changes on the makefiles, reflect the change on the MSVS build and test it. (I'm a MSVC user, but for the time being I use MinGW for the LLVM work). -- Oscar