similar to: [LLVMdev] CMake Win64 build status

I'm trying to build LLVM 3.3 using cmake/nmake, Microsoft C++ 2012, on a 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test case first and that appeared to work, then with the 64-bit compiler in the hope that would give me a 64-bit build of LLVM, but instead got this error message: [ 86%] Generating X86CompilationCallback_Win64.obj Microsoft (R) Macro Assembler (x64)

Hi Russel, I never tried to build LLVM with nmake. With msbuild it works without problems. You can find a short desription here: http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC, section Build LLVM. Regards Kai On 24.08.2013 21:15, Russell Wallace wrote: > I'm trying to build LLVM 3.3 using cmake/nmake, Microsoft C++ 2012, on a > 64-bit Windows 7 system. I

After some running some more tests, a weird addendum to this case: the build also fails at the same place with the same error message if MinGW isn't in the path. I'm not talking about MinGW instead of Microsoft C++, it's just that the build works if and only if MinGW is in the path _as well as_ the 32-bit version of Microsoft C++. On Sat, Aug 24, 2013 at 8:15 PM, Russell Wallace

... Or maybe not? I just tried it again in the exact same configuration that did work before, and this time it fails at an earlier stage with a different error: [ 66%] Building CXX object lib/Target/Mips/CMakeFiles/LLVMMipsCodeGen.dir/Mips16FrameLowering.cpp.obj Mips16FrameLowering.cpp NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~2.0\VC\bin\cl.exe' : return code '0xffffffff'

Hi Steve, On Thu, 15 Jan 2009, steve naroff wrote: > For development, CMake is working great for me. I rarely get build > errors related to the project file being out-of-date. > > Is it true that CMake only generates absolute paths? Any idea on the > difficulty of generating relative paths? I consider this a pretty big > obstacle... I did not follow the full-thread, just

These are the updated .sln and .vcproj files for building llvm with MSVC 2008. It turned out that the compiling errors were because these projects wasn't updated to reflect the actual status of the llvm files. I checked all the files (removed, moved or added) and now they are ok. It compiles all targets from the first "Build Solution", both for Debug and for Release mode. You need

lvqcl wrote: > 1) > Current MSVC solution (FLAC.sln and numerous .vcproj files) was made with > VC2005 Express and doesn't allow to build 64-bit files/libraries. > > IMHO it's time to add 64-bit support for MSVC builds, but AFAIK only Visual Studio > 2012/2013 Express are free and allow to build 64-bit files. > > VS 2005/2008 use .vcproj files, and VS

On Tue, 13 May 2008, Razvan Aciu wrote: > These are the updated .sln and .vcproj files for building llvm with MSVC > 2008. > It turned out that the compiling errors were because these projects wasn't > updated to reflect the actual status of the llvm files. > I checked all the files (removed, moved or added) and now they are ok. > It compiles all targets from the first

On Sun, Sep 21, 2008 at 9:27 AM, Óscar Fuentes <ofv at wanadoo.es> wrote: > This is an updated version of the patch that fixes some issues on VC++ > builds. Hi, FYI I just tried this (from r56534). I get an "error" (below) from cmake (2.6.1) about Intrinsics.gen but it seems to write out sln/vcproj anyway. Project.sln opens and builds OK (modulo a build error in llvmc2

Recently I downloaded MSVC++2005 Express Edition and it turns out that it wasn't possible to compile all files without several changes: 1) FLAC.sln has one extra "EndProject" line --- a\FLAC.sln 2013-06-17 11:57:09.000000000 +0400 +++ b\FLAC.sln 2013-08-16 20:19:34.630486700 +0400 @@ -157,7 +157,6 @@ EndProject Project("{4cefbc7c-c215-11db-8314-0800200c9a66}") =

Patrick Boettcher <pb at linuxtv.org> writes: >> For development, CMake is working great for me. I rarely get build >> errors related to the project file being out-of-date. >> >> Is it true that CMake only generates absolute paths? Any idea on the >> difficulty of generating relative paths? I consider this a pretty big >> obstacle... > > I did not

I verified the patch and it compiles all the targets, both in Debug and Release modes. If there is no someone else to keep the MSVC projects files updated, I will try from time to time to update them and to add the new targets. Maybe a note must be put in "docs/GettingStartedVS.html" at the Requirements section that llvm needs now MSVC (Express) 2008 to compile. Razvan -----

Hi Oscar, For development, CMake is working great for me. I rarely get build errors related to the project file being out-of-date. Is it true that CMake only generates absolute paths? Any idea on the difficulty of generating relative paths? I consider this a pretty big obstacle... Thanks for all your hard work on this, snaroff On Jan 15, 2009, at 9:46 AM, Óscar Fuentes wrote: >

I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are gone now). The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for

lvqcl wrote: > lvqcl wrote: > > > The patch does the following: > > Does the patch work for linux git? Windows git cannot apply a patch > that was created itself. It looks like that patch was created with the 'git diff' command and hence cannot be applied using the 'git am' command. It does however apply using the patch command. > (It writes LF in

lvqcl wrote: > Audacity still uses VS2008 and slowly tries to migrate to VS2012. > But as stated at <http://wiki.audacityteam.org/wiki/Developing_On_Windows>, > "Audacity is currently a 32-bit only application". So it doesn't need > 64-bit builds. > Currently its trunk contains 'audacity.sln' made with Visual C++ Express 2008 > and

Brendan Bolles wrote: > Phew! I figured it out. > > The FLAC .vcproj files link against "Multi-threaded" instead of > "Multi-threaded DLL". Made the change and things mostly fell into place. Was that a problem in the vcproj files shipped with FLAC or your own personal ones? If it was for the ones shipped with FLAC would you be able to provide a patch or even

Hi Dmitri, For what version of VS did you update the project files? Ted On May 17, 2008, at 3:00 PM, Dmitri Makarov wrote: > attached is the diff of vcprojs that need to be changed to fix the VS > build as of revision: 51224. > > I don't know if this catches all the missing bits, but this does build > all the way through. > > > Index: win32/Analysis/Analysis.vcproj

Hello, Following some recent messages about building with Visual Studio 2010, I have gotten most things to compile in release mode on 64b windows 7. (Mainly the few errors with 0 -> nullptr in the second argument of the pair constructor, and making an ECValue constructor public). I'm falling at the last hurdle though when it comes to the final link: 1>------ Build started: Project:

IMHO, the CMake-based build system is almost complete enough to replace current MSVC++ project files (modulo some community review and bug-fixing). Is this enough for adding it to the LLVM repo? >From the point of view of a MSVC++ user, the new build system is trivial to maintain: you can add a new library or tool executable in less time that it takes to open the project file on MSVC++, it