Re: Building glib-genmarshal (while building glib)

[Chun-wei Fan (范君維) <fanc999 yahoo com tw>]

Hi John,

Take a look at this commit in GLib[1] for glib-genmarshal.  So, for 
Windows, after running the script to generate glib-genmarshal, assuming 
that you are running it in cmd.exe or your Visual Studio projects, 
instead of running it as "glib-genmarshal(.exe) <your arguments to it>", 
you do "<your Python interpretor> <path to glib-genmarshal> <your 
arguments to it>", as you would running a Python script.  Note that I 
dropped the projects to build glib-genmarshal.exe from the Visual Studio 
projects.

You have to do likewise for glib-mkenums, by changing "<your PERL 
interpretor> <path to glib-mkenums> ..." to "<your Python interpretor> 
<path to glib-mkenums> ..."

With blessings, and cheers!

[1]: 
https://git.gnome.org/browse/glib/commit/?id=a00e7ed32e510791016725ce0a3dc08f59b9a443


John Emmas 於 2017/8/13 上午 01:34 寫道:
> On 12/08/2017 17:51, Bastien Nocera wrote:
> > There's no C to generate, it's been ported to Python.
> So 'glib-genmarshal.exe' doesn't need to get generated any more? When 
> I read about the port to python, I assumed it was just that the 
> original perl scripts had been ported to python.
>
> For glib-mkenums, the 'C' files are still getting generated, I think 
> (gioenumtypes.c + gioenumtypes.h) ?.  Maybe I'm wrong about that...
>
> John
> _______________________________________________
> gtk-devel-list mailing list
> gtk-devel-list gnome org
> https://mail.gnome.org/mailman/listinfo/gtk-devel-list