search for: intdir

...quot;..\..\lib\System\Win32\DynamicLibrary.cpp"> > > <FileConfiguration > > Name="Debug|Win32" > > ExcludedFromBuild="TRUE"> > > <Tool > > Name="VCCLCompilerTool" > > ObjectFile="$(IntDir)/$(InputName)1.obj"/> > > </FileConfiguration> > > <FileConfiguration > > Name="Release|Win32" > > ExcludedFromBuild="TRUE"> > > <Tool > > Name="VCCLCompilerTool" > > Ob...

...gt; > </File> > <File > RelativePath="..\..\lib\Transforms\Utils\SimplifyCFG.cpp"> > <FileConfiguration > Name="Debug|Win32"> > <Tool > Name="VCCLCompilerTool" > ObjectFile="$(IntDir)/$(InputName)1.obj"/> > </FileConfiguration> > <FileConfiguration > Name="Release|Win32"> > <Tool > Name="VCCLCompilerTool" > ObjectFile="$(IntDir)/$(InputName)1.obj"/> > </FileC...

...n32 Debug" # Begin Group "ASM" # PROP Default_Filter "nasm" # Begin Source File SOURCE=.\ia32\cpu_asm.nasm !IF "$(CFG)" == "libFLAC - Win32 Release" # Begin Custom Build InputPath=.\ia32\cpu_asm.nasm "ia32/cpu_asm.obj" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)" nasmw -f win32 -d OBJ_FORMAT_win32 -i ia32/ ia32/cpu_asm.nasm -o\ ia32/cpu_asm.obj !ELSEIF "$(CFG)" == "libFLAC - Win32 Debug" # Begin Custom Build InputPath=.\ia32\cpu_asm.nasm "ia32/cpu_asm.obj" : $(SOURCE) "$(INTDIR)" &qu...

...This problem is the motivation for having the _X86TargetMachineModule > symbol in LLVM. I thought this problem was solved by explictly list the object files in the "Additional Dependencies" of the project file? win32/llc/llc.vcproj: AdditionalDependencies="$(SolutionDir)X86\$(IntDir)\X86TargetMachine.obj $(SolutionDir)\CBackend\$(IntDir)\Writer.obj" -- Tzu-Chien Chiu, 3D Graphics Hardware Architect <URL:http://www.csie.nctu.edu.tw/~jwchiu>

...would have ??? :( These should really be fixed, for consistancies sake, presumably they produce warnings on 2003 and GCC. I have added dummy constructors in return statements to allow these to be compiled. Relative tool paths -------------------------- Relative tool paths like '..\TableGen\$(IntDir)\TableGen.exe' do not work on 2005, I have replaced them with '..\$(IntDir)\TableGen.exe', this puts all results in 'Win32/Release' for now. Misc Define ----------------- bugpoint/OptimizerDriver.cpp needs PLATFORMINDEPENDENT define to compile without 'sys/wait.h' miss...

...Command(s):C:/Utils/ninja.exe cmTC_009c0 && [1/2] Building C object CMakeFiles\cmTC_009c0.dir\testCCom piler.c.obj [2/2] Linking C executable cmTC_009c0.exe FAILED: cmTC_009c0.exe cmd.exe /C "cd . && "C:\Program Files\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_009c0.dir --r c=rc --mt=CMAKE_MT-NOTFOUND --manifests -- C:\PROGRA~2\MIB055~1\2019\COMMUN~1\VC\Tools\MSVC\1426~1.288\bin\Hostx64\ x64\link.exe /nologo CMakeFiles\cmTC_009c0.dir\testCCompiler.c.obj /out:cmTC_009c0.exe /implib:cmTC_009c0.lib /pdb: cmTC_009c0.pdb /version:0.0 /machin...

...b\System\Win32\Signals.cpp"> > <FileConfiguration > - Name="Debug|Win32" > - ExcludedFromBuild="TRUE"> > + Name="Debug|Win32"> > <Tool > Name="VCCLCompilerTool" > ObjectFile="$(IntDir)/$(InputName)1.obj"/> > </FileConfiguration> > <FileConfiguration > - Name="Release|Win32" > - ExcludedFromBuild="TRUE"> > + Name="Release|Win32"> > <Tool > Name="VCCLCompilerTool&qu...

Hi, when I updated the sources today there were several small problems that stopped the windows version from compiling, here are the patches m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: win32patches.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041115/34634455/attachment.txt>

...</PropertyGroup> <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'"> - <CustomBuildBeforeTargets>Compile</CustomBuildBeforeTargets> + <CustomBuildBeforeTargets> + </CustomBuildBeforeTargets> <IntDir>$(Platform)\$(Configuration)\$(ProjectName)\</IntDir> <OutDir>$(Platform)\$(Configuration)\</OutDir> </PropertyGroup> <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='ReleaseDLL|x64'"> - <CustomBuildBeforeTargets&...

I built my first submission with Visual Studio, but everything I read and watch suggests Ninja, about which I know nothing. Is it okay if I rerun CMake with -G "Ninja" in the same build directory, then just run ninja?

...in my configuration that is wrong for this setup? Or is this build configuration not supported at all? Thanks for the help, Tobias [285/1938] Linking CXX executable bin\llvm-tblgen.exe FAILED: bin/llvm-tblgen.exe cmd.exe /C "cd . && C:\.conan\6785u87h\1\bin\cmake.exe -E vs_link_exe --intdir=utils\TableGen\CMakeFiles\llvm-tblgen.dir --manifests -- C:\code\clang-builder\src\bootstrap\bin\lld-link.exe /nologo utils\TableGen\CMakeFiles\llvm-tblgen.dir\AsmMatcherEmitter.cpp.obj utils\TableGen\CMakeFiles\llvm-tblgen.dir\AsmWriterEmitter.cpp.obj utils\TableGen\CMakeFiles\llvm-tblgen.dir\Asm...

Hi, I’d just like to interject to say that building within Visual Studio isn’t really that bad. Running the lit tests is a bit painful because the LLVM build tools that are integrated with the build system don’t play nice with msbuild. Particularly, I’ve never been able to actually cancel an invocation of lit or tablegen via visual studio. That said, there is a huge upside to building with