<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - create VSProject files for code editing in MSVS from gbuild" href="https://bugs.freedesktop.org/show_bug.cgi?id=70414#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - create VSProject files for code editing in MSVS from gbuild" href="https://bugs.freedesktop.org/show_bug.cgi?id=70414">bug 70414</a> from <a class="email" href="mailto:bjoern.michaelsen@canonical.com" title="Björn Michaelsen <bjoern.michaelsen@canonical.com>"> Björn Michaelsen</a> <pre>(In reply to <a href="show_bug.cgi?id=70414#c4">comment #4</a>) > Heh - sure, I was thinking of parsing the generated gnumake rules and deps > etc. from running a similar (but plunging) 'make -n -p' on an autotools > project; all previous attempts I've seen to parse auto* ended in dismal > failure ;-) but extending this approach would work nicely I think. Possible maybe. But since autotools uses a lot of recursive make, one would need to walk the dirs and then make sense of it by merging the pieces into one big view of the thing adding context here and there.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>