[01:38:23] <FONT COLOR="#008080">---</FONT> <font color="#616161">DominusExult is now known as Dominus</font><BR>
[08:33:38] &lt;<font color="#600060">Dominus</font>&gt; why is building Exult with mingw so slooooooow :)<BR>
[08:38:14] &lt;<font color="#600060">Dominus</font>&gt; But seriously, Marzo, do you have any idea how to handle my cross compiling woes? it all boils down to two issues now:<BR>
[08:40:00] &lt;<font color="#600060">Dominus</font>&gt; 1. in makefile.common that it executes "expack$(EXEEXT)" - for cross compile I would need to execute expack, and at best have a EXPACK variable that can point to the path of expack (as I've added elsewhere for cross compile via ./configure)<BR>
[08:40:47] &lt;<font color="#600060">Dominus</font>&gt; 2. in makefile.mingw a way to set a different windres and dllwrap<BR>
[08:41:32] &lt;<font color="#600060">Dominus</font>&gt; maybe adding a $(TARGET) in front would work already. <BR>
[08:42:12] &lt;<font color="#005000">Marzo</font>&gt; Building with mingw is slow because of 2 things: 1. you probably are not passing -j&lt;N&gt; for more jobs; and 2. process creation in Windows is very slow<BR>
[08:42:35] &lt;<font color="#005000">Marzo</font>&gt; You should see how slow ./configure is on Windows compared to Linux/OSX<BR>
[08:43:03] &lt;<font color="#600060">Dominus</font>&gt; I'm setting TARGET in the cross-make.sh https://pastebin.com/4KiU5rcH and the binary names are i686-w64-mingw32-dllwrap i686-w64-mingw32-windres<BR>
[08:43:07] &lt;<font color="#005000">Marzo</font>&gt; And the reason why I wantd to setup AppVeyor for this is it does a native Windows build<BR>
[08:43:14] &lt;<font color="#005000">Marzo</font>&gt; So no need for cross-compilation<BR>
[08:43:42] &lt;<font color="#600060">Dominus</font>&gt; yeah, I did pass on -j but still... phew :)<BR>
[08:44:53] &lt;<font color="#600060">Dominus</font>&gt; but I am surprised that eventually it did create the exult.exe :)<BR>
[08:45:08] &lt;<font color="#600060">Dominus</font>&gt; now I need to test whether it actually works<BR>
[08:45:12] &lt;<font color="#005000">Marzo</font>&gt; In fact, sometimes builds even fail in mingw because quickly creating and destroying a lot of processes (i.e., running lots of programs; this is dirt cheap in Linux) is expensive enough in Windows that it causes a process creation to fail<BR>
[08:46:52] &lt;<font color="#600060">Dominus</font>&gt; and it fails to run on a real Windows :(<BR>
[08:53:54] &lt;<font color="#0000C0">azeem</font>&gt; are there plans to switch to a different build system? Guess not, cause it's a lot of work. If not, I can open a branch and start working on making the autotools build system "make dist" compliant in case I find time<BR>
[08:54:08] &lt;<font color="#0000C0">azeem</font>&gt; or is this something that's not really needed/wanted?<BR>
[08:59:16] &lt;<font color="#600060">Dominus</font>&gt; I definitely would not like to switch build systems :) but make dist would be nice to have<BR>
[09:00:53] &lt;<font color="#0000C0">azeem</font>&gt; ok<BR>
[09:01:55] &lt;<font color="#0000C0">azeem</font>&gt; switching to cmake would have the advantage that you'd only one build system for Linux/MacOS/Windows, but I think it'd be too much work with unclear risks<BR>
[09:03:02] &lt;<font color="#600060">Dominus</font>&gt; yes, that's my takeaway, too<BR>
[09:49:07] <FONT COLOR="#008080">---</FONT> <font color="#616161">uohcmjzxpdpnqvnz is now known as mzjyaatvahnxtjyy</font><BR>
[09:49:11] <FONT COLOR="#008080">---</FONT> <font color="#616161">mzjyaatvahnxtjyy is now known as Marzo</font><BR>
[20:53:18] &lt;<font color="#600060">Dominus</font>&gt; awwww that fucker deleted my stickied posts, it seems<BR>