Hi John, are you using https://github.com/nice-software/gtk-win32/ ? If not, any reason to not use it and improve it for your use case?
Cheers. On Wed, May 13, 2015 at 9:59 AM, John Emmas <john...@tiscali.co.uk> wrote: > I'm building Glib (from Git) using MSVC. FWIW I use my own MSVC projects > (rather than the supplied ones) although that isn't relevant here. What's > relevant is that, while building libgio, a bunch of python files get > converted to binary equivalents. This is all connected with gdbus-codegen > AFAICR. For example, there's a python source called "codegen_main.py" > which gets converted to "codegen_main.pyc". The build procedure has been > working perfectly for many years. > > For reasons unconnected with Glib I needed to upgrade python yesterday to > ver 3.3.5. Since the upgrade, my python binaries now have different > names. For example, the above binary now gets called:- > > codegen_main.cpython-33.pyc > > I don't know enough about the build process to know whether there might be > any ramifications caused by the name changes. Are the ".pyc" files just > used internally by python itself (in other words, the name isn't > important)? Or could there be other ramifications for my build? I realise > I should be contacting the python team - but I wanted to ask some advice > first to find out if anyone can anticipate any potential problems from this > change? Thanks. > > John > _______________________________________________ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gtk-devel-list > -- Ignacio Casal Quinteiro
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list