search for: inputpath

Displaying 7 results from an estimated 7 matches for "inputpath".

2004 Sep 10
2
stat() and Windows
...gin Target # Name "libFLAC - Win32 Release" # Name "libFLAC - Win32 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...
2004 Dec 03
0
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
...th="..\..\utils\TableGen\FileLexer.l"> > > <FileConfiguration > > Name="Debug|Win32"> > > <Tool > > Name="VCCustomBuildTool" > > CommandLine="..\tools\flex -t &gt;$(InputDir)$(InputName).cpp $(InputPath) > > " > > Outputs="$(InputDir)$(InputName).cpp"/> > > </FileConfiguration> > > <FileConfiguration > > Name="Release|Win32"> > > <Tool > > Name="VCCustomBuildTool" > >...
2004 Dec 03
2
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
...;File > RelativePath="..\..\utils\TableGen\FileLexer.l"> > <FileConfiguration > Name="Debug|Win32"> > <Tool > Name="VCCustomBuildTool" > CommandLine="..\tools\flex -t &gt;$(InputDir)$(InputName).cpp $(InputPath) > " > Outputs="$(InputDir)$(InputName).cpp"/> > </FileConfiguration> > <FileConfiguration > Name="Release|Win32"> > <Tool > Name="VCCustomBuildTool" > CommandLine="..\tools\flex -t...
2008 Feb 18
3
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
...at's happening from within the .sln script--am I missing a >pre-build step someplace? When config.h.in is hit in the build of configure the configure project, the configure.h file from the win32 directory is copied to main llvm\Config\Config.h. The script in the sln file is: copy "$(InputPath)"+"$(SolutionDir)config.h" "$(ProjectDir)..\llvm\Config\config.h" configured as a custom build step in the solution file. Is that not firing from the command line compilation of the sln? The file in the win32 directory is the config.h file that's ultimately used when...
2008 Feb 19
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
...script--am I missing a > >pre-build step someplace? > > When config.h.in is hit in the build of configure the configure > project, > the configure.h file from the win32 directory is copied to main > llvm\Config\Config.h. The script in the sln file is: > > copy "$(InputPath)"+"$(SolutionDir)config.h" > "$(ProjectDir)..\llvm\Config\config.h" > > configured as a custom build step in the solution file. Is that not > firing from the command line compilation of the sln? > > The file in the win32 directory is the config.h file t...
2008 Feb 18
0
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
More on this: Walking through the projects slowly: (*) "Configure" builds with no problem. (*) "support" fails: C:\Prg\llvm-2.2\llvm-2.2\win32>msbuild llvm.sln /t:Build Microsoft (R) Build Engine Version 2.0.50727.1433 [Microsoft .NET Framework, Version 2.0.50727.1433] Copyright (C) Microsoft Corporation 2005. All rights reserved. Build started 2/18/2008 12:07:45 AM.
2008 Feb 18
2
[LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005?
By the way, somebody (I think it was Chuck, but I don't remember for certain) was asking for the BuildLog.htm from building the llvm.sln file under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured to produce a new BuildLog for each and every one of the projects inside the solution. I don't know who's responsible for this guy, but that's probably not the best way