Hi Alexander,<br><br>Thanks for your quick response!<br><br><div class="gmail_quote">2008/10/24 Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Friday 24 October 2008, Alexander Neundorf wrote:<br>
><br>
> Yes, I think you're the first one who tries that.<br>
></div></div></blockquote><div><br>Alright! =)<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="Wj3C7c"><br>
> > This is the custom build step I need to perform (copy pasted from a<br>
> > handcrafted solution file):<br>
> ><br>
> > ml64 -c -Zi "-Flfoobar.lst" "-FRfoobar.sbr" "-Fofoobar.obj" "foobar.asm"<br>
><br>
> Are -Fl and -FR necessary or does it also work without them ?<br>
></div></div></blockquote><div><br>The foobar.lst one isn't necessary. The second one only is necessary if browse information is needed. Not sure if that is the case ...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c"><br></div></div>Ok, it was a bit faster (waiting for Qt to build...)<br>
<br>
So, please put the three attached files into the cmake Modules/ directory and<br>
use<br>
ENABLE_LANGUAGE(ASM-MASM)<br>
This should find ml64.exe .<br>
If it doesn't, try hardcoding it for now in<br>
CMakeDetermineASM-MASMCompiler.cmake.<br>
Let me know which problems you hit.<br>
<br>
Alex<br>
</blockquote></div><br>I already tried something similar, though I got stuck halfway.<br>Anyway, I dropped in your files in my source directory, which I've added to the module path as follows:<br><br>list(APPEND CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR})<br>
<br>cmake seems to pick them up alright. But the result doesn't seem to work.<br><br>I've tried it in two ways:<br><br>1. Using the Visual Studio 2005 Win64 generator to create solution files<br><br>- Here the minor problem is, as you already predicted, that it doesn't automatically detect ml64.exe but a manual configuration of the variable does help<br>
- the asm file appears in the project, but there doesn't seem to be any build rule associated with it. Nor as a custom build step in the properties pages, nor as a CMake rule<br>- as a result, the asm file does not get build, yielding some unresolved symbols at linking time<br>
<br>2. Using nmake from the VS2005 x64 command prompt<br><br>- The first issue is that nmake doesn't like the dashes in variable/macro names. So I had to replace it by an underscore in the dialect strings:<br><br>SET(ASM_DIALECT "_MASM")<br>
<br>- Again, no build rule for the asm file gets inserted, resulting again in unresolved symbols.<br>- Then it dawned to me that there were other places to replace -MASM by _MASM: in enable_language, when setting the asm file's language property, and also in the filenames of the cmake files you gave me.<br>
- Now, build rules are created, but no obj files are being build. I had to move <SOURCE> to the end:<br><br>SET(CMAKE_ASM${ASM_DIALECT}_COMPILE_OBJECT "<CMAKE_ASM${ASM_DIALECT}_COMPILER> <FLAGS> /c /Fo <OBJECT> <SOURCE>")<br>
<br>- Now, obj file is build, it is enlisted in objects.rsp, but the linker still can't find its symbols ...<br><br>But at least, we're one or two steps closer =)<br><br>1. Why doesn't the asm file get any rules in the solution file?<br>
2. Why are the symbols still unresolved in the nmake situation?<br><br>Cheers,<br>Bram<br><br>-- <br>hi, i'm a signature viruz, plz set me as your signature and help me spread :)<br>