https://bugs.freedesktop.org/show_bug.cgi?id=70414
Priority: medium
Bug ID: 70414
Assignee: [email protected]
Summary: create VSProject files for code editing in MSVS from
gbuild
Severity: minor
Classification: Unclassified
OS: Windows (All)
Reporter: [email protected]
Hardware: Other
Status: UNCONFIRMED
Version: unspecified
Component: Libreoffice
Product: LibreOffice
Created attachment 87541
--> https://bugs.freedesktop.org/attachment.cgi?id=87541&action=edit
definitions about a library
If you run e.g.:
make cmd make -npf Makefile.gbuild all
you will get a huge output of gbuilds state (without actually building
anything). It should also contain a piece of text like the attached one
describing ~completely (include paths, compile flags, link flags, source files
...) how each library gets build.
This EasyHack is to create a script (or better a make target wrapping a
script), that:
- finds that data in the output
- extract that data
- and generate a VS Project file, that allows to load the library as a project
in VS with include paths etc. set so that InteliSense (code completing) works
In the first step it is NOT required to allow building directly from VS. Later,
bonuspoints might get earned with extending the generated project files to
trigger gbuild from VS with a Custom Action:
http://msdn.microsoft.com/en-us/library/vstudio/d9k65z2d%28v=vs.100%29.aspx
So for starters, this is to allow Windows developers to continue using MSVS as
an editor and IDE. Do NOT attempt a perfect 1:1 translation, ability to edit
with code completion should be enough for starters!
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
