RE: MSVC compilation of the *mm core stack from master

[<marcmicalizzi gmail com>]

Unfortunately the VCPKG version is only at gtkmm-3.22.2, whereas I'm trying
to build gtk4 (3.9x.x), and seeing as the actual releases of gtkmm are few
and far between (last release was 3.93.0 on 2018-02-24, which I actually
couldn't get to build under windows against gtk+ 3.93.0, also gtk+'s last
release was 3.94.0 on 2018-06-26 with no matching gtkmm release), it seems
that going from git master it the only real option to keep up with fixes and
changes in the unstable branch. 

Under linux, this would be fine as jhbuild handles everything (mostly),
however under Windows msvc++, the only way I've found to do it is a much
more manual process, as mentioned previously, of using jhbuild on linux the
generate the files, and then filling in the gaps, which isn't quite enough
this time around.

Thanks,
Marc

-----Original Message-----
From: Kasper Peeters <kasper peeters phi-sci com> 
Sent: November 22, 2018 11:25 AM
To: Marc Micalizzi via gtkmm-list <gtkmm-list gnome org>
Cc: marcmicalizzi gmail com
Subject: Re: MSVC compilation of the *mm core stack from master

I know this does not answer your question, but I found that the gtkmm and
related packages in Microsoft's VCPKG at https://github.com/Microsoft/vcpkg
work very well, and save you the hassle of setting up this build process
yourself.

To anyone trying to setup gtkmm on Windows, feel free to email me for
details.

Cheers,
Kasper


On Thu, 22 Nov 2018 11:20:12 -0500
Marc Micalizzi via gtkmm-list <gtkmm-list gnome org> wrote:

> Since recently the MSVC projects seem to have been dropped and 
> switched over to nmake for MSVC, I've gotten stuck on compiling the 
> stack at glibmm:
>
> NMAKE : fatal error U1073: don't know how to make 
> 'release\x64\glibmm\glibmm.res'
>
>  
>
> Given that I have been unable to find any documentation or 
> instructions on compiling on msvc from master, the only way I've 
> managed to figure out or find for even compiling from master on msvc 
> native (without using mingw or cygwin, so-as to avoid linking to any 
> mingw or cygwin dlls) is using jhbuild on linux and then copy the 
> generated .cc and .h files over to windows, and then build using those 
> (and usually taking the *config.h files from a build of whichever 
> library it is from ftp.gnome.org <ftp://ftp.gnome.org> , comparing to 
> the new one, and making changes). Is there a better way to do this? It 
> wasn't able to find glibmm.res for the nmake build from jhbuild.
>
>  
>
> Thanks!