<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#c4">Comment # 4</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:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> Michael Meeks</a> <pre>> As for extending this to autotoolsy projects Im not sure if that is so easy. > It it really trivial to extract the build information from gbuild as it is > exportable in a really easy to parse way, while autotools defies parsing > even by most humans judging from a nonscientific survey in my environment 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>