<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Message: 7<br>
Date: Mon, 27 Oct 2008 23:06:22 +0100<br>
From: Alexander Neundorf <<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>><br>
Subject: Re: [CMake] assembly files with masm in vs2005 64bit<br>
To: <a href="mailto:cmake@cmake.org">cmake@cmake.org</a><br>
Message-ID: <<a href="mailto:200810272306.22665.a.neundorf-work@gmx.net">200810272306.22665.a.neundorf-work@gmx.net</a>><br>
Content-Type: text/plain; charset="iso-8859-6"<br>
<br>
Hi Bram,<br>
<br>
Please test the attached files.<br>
They still shouldn't find ml64.exe, but I added some debug output I'd like to<br>
see. So, please use them and post the output.<br>
In which directory is ml64.exe on your system ?<br>
<br>
Alex<br>
</blockquote><div><br>Hi Alex,<br><br>On the nmake front: the problem with the unresolved symbols is one of building a DLL instead of static library, and the symbols don't get exported ... So, at least, I'm successful at using masm with nmake.<br>
<br>That still leaves open the issue of the visual studio projects not including any build rule for the assembly. So it's not a build rule that fails, but it is simply missing ...<br><br>Here's the output you requested for <br>
<br>Visual Studio 2005 Win64 generator:<br><br>Check for working C compiler: cl<br>Check for working C compiler: cl -- works<br>Detecting C compiler ABI info<br>Detecting C compiler ABI info - done<br>Check for working CXX compiler: cl<br>
Check for working CXX compiler: cl -- works<br>Detecting CXX compiler ABI info<br>Detecting CXX compiler ABI info - done<br>CMAKE_C_COMPILER_PATH: -<br>CMAKE_C_COMPILER: -cl<br>TOOLCHAIN LOCATION: -<br>Didn't find assembler<br>
Loaded CMakeASM_MASMInformation - ASM_MASM support is still experimental, please report issues<br>Configuring done<br><br>For comparison, this is what I get using the nmake generator (which immediately gives you the locations requested for. it can be assumed ml64.exe is next to cl.exe):<br>
<br>The C compiler identification is MSVC<br>The CXX compiler identification is MSVC<br>Check for CL compiler version<br>Check for CL compiler version - 1400<br>Check if this is a free VC compiler<br>Check if this is a free VC compiler - no<br>
Check CL platform<br>Check CL platform - 64 bit<br>Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/cl.exe<br>Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/cl.exe -- works<br>
Detecting C compiler ABI info<br>Detecting C compiler ABI info - done<br>Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/cl.exe<br>Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/cl.exe -- works<br>
Detecting CXX compiler ABI info<br>Detecting CXX compiler ABI info - done<br>CMAKE_C_COMPILER_PATH: -<br>CMAKE_C_COMPILER: -C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/cl.exe<br>TOOLCHAIN LOCATION: -C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64<br>
Found assembler: C:/Program Files (x86)/Microsoft Visual Studio 8/VC/bin/amd64/ml64.exe<br>Loaded CMakeASM_MASMInformation - ASM_MASM support is still experimental, please report issues<br><br>Thanks for your help,<br>Bram<br>
<br></div></div><br>-- <br>hi, i'm a signature viruz, plz set me as your signature and help me spread :)<br>