On 05/02/2016 12:36 PM, Lucas Levrel wrote: > […] > > I'm not an expert programmer and when I wanted to compile for Windows > the software I developped in Linux, I couldn't achieve a satisfactory > result (using the -mwin32 or -mwindows flag gave either a clumsy > additional command window, or yielded an antivirus alert!). > > Then I found MinGW Cross Env, now called MXE (http://mxe.cc/). It > compiled my project with no effort at all. When you install it, it > compiles the cross-compiler and the libs you want, so this takes quite > long, but with no user intervention. Then all you have to do is add such > lines in your Linux-ready Makefile: > > # prepend all binaries with a later-defined prefix > PKG_CONFIG=$(CROSS)pkg-config > CXX=$(CROSS)g++ > LD=$(CROSS)ld > AR=$(CROSS)ar > STRIP=$(CROSS)strip > ... > # define the prefix in the rules targeting Windows > myrule : CROSS=/path/to/bin/i686-pc-mingw32- > myrule : ... > > HTH >
This is interesting. May I hijack this thread? I did not know about MXE. What is their relationship with MSYS2? Distributing the GTK+ source code with bundles for LGPL compliance seems easier with MXE. How do others handle source code distribution? This is not an issue for GNOME projects and I can't find examples. Is it really necessary for every Windows application bundle to ship its own copy of GTK+? Regards, Florian _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
