<br>Chaps,<br><br><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;">Michael O'Shea wrote:<br>
> People,<br>
><br>
> you may have seen me on IRC discussing the building of amarokplasmalib<br>
> in MSVC. I don't actually want to obtain anything that can execute, I<br>
> just want to use MSVC's call mapping tools to analyse the dependencies<br>
> between different libraries. This requires that I be able to finish<br>
> building objects properly.<br>
<br>
I'm not sure I understand your issue. If you just want object files, why<br>
can't you just run "emerge amarok"? Sure, you'll end up with something<br>
you can execute as a by-product, but it'll produce the object files<br>
along the way.</blockquote><div><br>I actually don't want the object files. I want the "program database" files that MSVC produces as it compiles the source and in which it keeps all sorts of metadata on such things as "call maps" which is what *I* am interested in.<br>
<br>Like I said earlier on : I want to use the call mapping capability of MSVC in order to work out dependencies between different code modules.<br><br>Naturally, if MinGW (whatever the alternative to MSVC is) can do this too, I'll drop MSVC and go and build with the other alternative instead.<br>
<br>So, is there anyone out there with experience in building with MSVC who could help ?<br><br>Cheers,<br><br>Michael<br></div></div><br>