Re: Compiling for Windows [Was: argv revisited]

2016-05-06 Thread tito-wolit
On 05/06/2016 09:27 PM, Andrew Robinson wrote: I'm sorry for that. One of my biggest flaws in human relations is detecting when someone is being ironic, sarcastic, or is just joking around, and when they are being serious. I would think both list would be interested in knowing what is required

Re: Compiling for Windows [Was: argv revisited]

2016-05-06 Thread Florian Pelz
On 05/06/2016 07:01 PM, Lucas Levrel wrote: > Le 5 mai 2016, Andrew Robinson a écrit : >> 1) Because there are between 40 to 120Mb worth of libraries or their >> dependencies I would have to post on my website. > > It's not clear to me whether one has to distribute GTK if it's linked > statically,

Re: Compiling for Windows [Was: argv revisited]

2016-05-04 Thread Matthew A. Postiff
Try this package: $ pacman -Ss mingw-w64-i686-gtk3 mingw32/mingw-w64-i686-gtk3 3.18.6-1 [installed] GObject-based multi-platform GUI toolkit (v3) (mingw-w64) On 5/4/2016 3:51 PM, Andrew Robinson wrote: > Yeah, I see that, but that only downloads 64-bit binaries. I need the Win-32 > binaries.

Re: Compiling for Windows [Was: argv revisited]

2016-05-04 Thread Florian Pelz
On 05/04/2016 03:59 PM, Andrew Robinson wrote: > No, there are no Win32 binaries in MSYS2. Where are you getting your > information? > MSYS2 contains pacman. `pacman -Syu mingw-w64-x86_64-gtk3` downloads GTK+ binaries for x86_64 and puts them in the C:\msys64\mingw64 directory (by default). This

Re: Compiling for Windows [Was: argv revisited]

2016-05-04 Thread Florian Pelz
On 05/04/2016 02:22 AM, Andrew Robinson wrote: > I have an idea! Why doesn't someone just compile all the binaries for Win32 > and Win64 and make them available on the Internet, that way none of us will > have to go through all this stupid BS just to get some binaries? Just two > packages, one for

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Florian Pelz
On 05/03/2016 08:34 PM, Dov Grobgeld wrote: > The complete gtk run time is only about 20MB in size (at least for gtk2) > which with todays hard disk sizes really is negligable, so I agree that > there is no reason to try to create a common gtk runtime. > > I still remember the frustration back in

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Dov Grobgeld
Another equivalent scons-based way of compiling for windows with gcc is shown in my program giv. See: https://github.com/dov/giv/blob/master/SConstruct SCons uses the Sconstruct files to do the cross-compilation and also calls out to nsis to create a windows installer. The complete gtk run time

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Allin Cottrell
On Tue, 3 May 2016, Dave Howorth wrote: On 2016-05-03 16:57, Florian Pelz wrote: I'd like to have one standard GTK+ installer for the GTK+ DLLs etc. that can be downloaded and installed from other installers, so there is just one GTK+ installed on Windows instead of one copy of perhaps differen

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Florian Pelz
On 05/03/2016 06:12 PM, Dave Howorth wrote: > On 2016-05-03 16:57, Florian Pelz wrote: >> I'd like to have one standard GTK+ installer for the GTK+ DLLs etc. that >> can be downloaded and installed from other installers, so there is just >> one GTK+ installed on Windows instead of one copy of perha

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Dave Howorth
On 2016-05-03 16:57, Florian Pelz wrote: I'd like to have one standard GTK+ installer for the GTK+ DLLs etc. that can be downloaded and installed from other installers, so there is just one GTK+ installed on Windows instead of one copy of perhaps different versions of GTK+ for each application.

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Florian Pelz
On 05/03/2016 03:26 PM, Lucas Levrel wrote: > By default MXE links statically. So you don't have any dll to bundle > with your app. In such circumstances, what does LGPL say? Do you still > have to provide the GTK source code (given that you don't distribute GTK > libs)? > IANAL, but if the libra

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Florian Pelz
On 05/03/2016 04:57 PM, Andrew Robinson wrote: > Well I can't ship MSYS2 and MXE with my application, and I most certainly > can't sell any application to grandma and grandpa, if it requires instructions > on how to install MSYS2 and MXE just so you can run my application. > For MSYS2, you create

Re: Compiling for Windows [Was: argv revisited]

2016-05-03 Thread Lucas Levrel
Le 2 mai 2016, Florian Pelz a écrit : On 05/02/2016 12:36 PM, Lucas Levrel wrote: Then I found MinGW Cross Env, now called MXE (http://mxe.cc/). It compiled my project with no effort at all. This is interesting. May I hijack this thread? I did not know about MXE. What is their relationship w

Re: Compiling for Windows [Was: argv revisited]

2016-05-02 Thread Andrew Robinson
Thank you Lucas, for submitting this post. MXE seems very interesting and I feel compelled to do some more research into it. On 5/2/2016 at 3:36 AM, Lucas Levrel wrote: >(copy to OP in case he's already unsubscribed, apologies for duplication >if he's not) > >Le 30 avril 2016, Andrew Robinson a

Re: Compiling for Windows [Was: argv revisited]

2016-05-02 Thread Florian Pelz
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 yie