[PATCH 0/2] Compilation warning fixes
twasilczyk at pidgin.im
Tue May 13 04:38:09 EDT 2014
On 05/13/2014 05:11 AM, Felipe Contreras wrote:
> On Mon, May 12, 2014 at 3:43 AM, Tomasz Wasilczyk <twasilczyk at pidgin.im> wrote:
>> 12 maj 2014 08:35 "Felipe Contreras" <felipe.contreras at gmail.com>
>>> I've no idea why people are interested in
>>> libpurple-mini, but it seems there's quite a few.
>> Isn't it enough to compile official Pidgin with congifure switches that
>> disables Pidgin and Finch? I'm just curious.
> That might work in Linux, but I'm not so sure it would be so easy to
> compile for Windows.
With autotools - it is as trivial as in Linux.
> Moreover, I haven't actually tried it, but I bet my Makefile is at
> least an order of magnitude faster.
For Linux (and cross-compilation for win32 too), most of build time is
compilation, which is not affected by Makefiles.
>>> BTW. I saw in the archives some talk to use autotools for building on
>>> Windows which seems the absolute worst thing to do.
>> Some Pidgin devs also state that. But I still have no idea *why* is it the
>> worst thing to do. If we provide a repository with mingw dependencies it
>> will be repeatable. The only disadvantage I see is a longer build time on
>> Cygwin. But Cygwin is already a disaster.
> Have actually tried to run autotools in Windows? There's no perl,
> there's no m4. I wouldn't dream of doing that, particularly when pure
> make works just fine.
The initial set of patches for win32-autotools build came from a person
who didn't even tried to compile on linux. Personally, I'm not going to
run any more builds on Windows, since cross-compilation finally works
for 3.0.0 branch.
> I've worked all my professional life
> on embedded systems, and I can assure you; autotools are the worst for
I still don't know *why*. Yes, I had certain problems with autotools for
win32, but I've managed to fix those. I could also believe, that
autotools were a no-go for mingw-based cross compilation 10 years ago.
I *really* have no idea why autotools is the worst. I don't know any
issue about it.
>> I looked at the one you mentioned and I'm not sure if it handles
>> every quirk of every unix we build for.
> That's the whole reason you use GLib.
GLib won't handle everything. For example optional external libs and
dependencies between them (gtk2/3 vs webkitgtk vs gst0.10/1.0). Or (I'm
not sure about all of these)
socklen_t/sockaddr.sa_len/fileno/inet_aton/etc routines, that may be
missing on some systems.
Please note, that I'm not trying to insist (yet ;)) on dropping the
legacy win32 build. I'm trying to figure out the real issues behind the
unified buildsystem based on autotools.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4225 bytes
Desc: Kryptograficzna sygnatura S/MIME
More information about the Devel