[Bug 70414] create VSProject files for code editing in MSVS from gbuild

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. -- You are receiving this mail because: You are on the CC list for the bug.

Context

[Bug 70414] create VSProject files for code editing in MSVS from gbuild · bugzilla-daemon

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.