Displaying 3 results from an estimated 3 matches for "filetracker".
2019 Jan 25
2
MSBuild incremental builds are broken with LLVM 6 (and beyond)
Hi,
Starting with LLVM 6, MSBuild incremental builds stopped working. I've
tracked this down to a CL that modified how file renaming was done on
Windows. It appears that FileTracker does not recognize renaming a file
with SetFileInformationByHandle.
https://github.com/llvm-mirror/llvm/commit/1b6a51a1425cc0180359ecd64733edb965f65d7c#diff-70db51c38d748dc9debf5f309643fcd8
You can repro this fairly easily by:
1) Downloading the prebuilt binaries of LLVM 6 or 7 for Windows.
2) Cr...
2015 Jun 09
2
[LLVMdev] msbuild and clang
...ileLogger pcbuild.sln
(The second line is the one that substitutes clang-cl - with that removed,
everything is successful)
The build failed with the following error message:
Tracking command:
C:\Program Files (x86)\MSBuild\12.0\bin\Tracker.exe /d "C:\Program Files
(x86)\MSBuild\12.0\bin\FileTracker.dll" /i
C:\Python-2.7.10\PCbuild\x64-temp-Release\kill_python\kill_python.tlog /r
C:\PYTHON-2.7.10\PCBUILD\KILL_PYTHON.C /b
MSBuildConsole_CancelEvent306536dcec844c0c97517539ced8ed5d /c
C:\Python-2.7.10\PCbuild\CL.exe /c /I..\Include /I..\PC /Zi /nologo /W3
/WX- /O2 /Ob1 /Oi /GL /D _WIN64 /D...
2015 Jun 08
3
[LLVMdev] msbuild and clang
I'm trying to compile some large programs with clang on Windows (with a
view to compiling to bit code and then running some whole program
optimisations on the bit code).
Take for example the Python 2.7 interpreter:
As is typically the case, the usual build procedure involves running
msbuild which invokes the Microsoft compiler.
The most obvious procedure would then be to substitute