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

https://bugs.freedesktop.org/show_bug.cgi?id=70414

--- Comment #9 from Honza Havlíček <havlicek.honza@gmail.com> ---
There is somewhat working version in master, so progress report:

What works:
* It is possible to generate solution (collection of projects) for each module
that will contain C++ project for all Library_* and Executable_* in the the
module.
* You can build (calls make {project makefile}), rebuild (calls make calls make
{project makefile}.clean {project makefile}) and clean projects (calls make
{project makefile}.clean). Use context menu of project or define keyboard
shortcut (see below).
* There are multiple configurations, default one is for building projects, .
You can switch between them from drop down menu in the toolbar (the one with
text "Build" next to "Win32"). Other configuration are for unit testing and
integration tests.
* You can run LO by from menu Debug->Start Without Debugging and attach to it
(Debug-> Attach To Project, choose soffice.bin). Breakpoints work, you can
change content of variables in debugger and all that good stuff.

What doesn't work:
* No projects for unit tests (parser doesn't currently support them)
* When running LO from VS, it always says that project is out of date and if it
should be rebuild. How exactly does VS checks that is unclear, but it seems to
check for some .pdb file in build directory.
* There might also be one solution for all projects, in addition to per-module
solutions.
* Generation of projects only works when you run it in source directory, not
for different directory.
* When you build solution all projects are build in parallel (= a lot of make
module.build at once), that can probably lead to some trouble. Build only one
project at time. VS2012 Express doesn't have shortcut for building only one
project by default, I recomment defining it using Tools->
Options->Environment->Keyboard, Command "Build.BuildSelection" builds the
project currently active file is part of 

Notes:
Since VS2010, MS has changed the project file structure to MSBuild (something
like Ant). When VS builds project, it runs MSBuild file with target build.
Except build, there are also rebuild, clean and publish (though probably only
for some types of project). Instead of overriding targets in MSBuild, I used
NMake type of project, that allows user to change the command performed by VS
when target (build/rebuild/clean) is run in GUI: Project Properties ->
Configuration Properties -> NMake.

-- 
You are receiving this mail because:
You are on the CC list for the bug.