[06:57:29] <font color="#600060">Dominus:</font> Hey bot, still working?<BR>
[06:57:48] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> Yay!<BR>
[09:07:23] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> Marzo, the iOS CI runs in my fork https://github.com/DominusExult/exult/runs/8067117772?check_suite_focus=true (stripped the notifiy section). Should I commit?<BR>
[16:51:54] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Yes please<BR>
[17:00:39] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> On it, just wasn't sure if you wanted to do it differently for the libraries cloning 🙂<BR>
[17:04:10] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> @Dominus Just make sure to replace the lingering instances of 'macos' by 'ios' in the file<BR>
[17:04:34] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> did that 🙂<BR>
[19:42:18] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> @Marzo could the Android CI action be caused by the not up to date versions of ogg (1.3.4 vs 1.3.5) and vorbis (1.3.6 vs 1.3.7)?<BR>
[19:42:47] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Let me check<BR>
[19:46:57] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Nope, the dependencies used there are 1.3.5 and 1.3.7<BR>
[19:48:28] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> but the configure output is Ogg.........................: 1.3.4 338 Vorbis......................: 1.3.6<BR>
[19:48:39] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> that's why I wondered<BR>
[19:51:31] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> That is a bit misleading, actually<BR>
[19:51:59] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> As far as I can tell, building Exult normally as is done for the android port is useless and wasteful<BR>
[19:52:34] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Everything is built again from the android folder, and it uses some cmake to get and compile dependencies<BR>
[19:56:19] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> I see<BR>
[19:57:42] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> We need to swap Exult to cmake, and nuke the parallel build systems we have in-place<BR>
[19:58:00] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> This is one of the reasons I wanted to setup CI for Android and iOS<BR>
[19:58:13] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> So that I can create a branch, and hack away<BR>
[19:58:26] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> And if something breaks the build, I will have feedback<BR>
[19:59:10] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> I will start working on ignoring most of the autoconf/automake stuff and base the cmake stuff on the MinGW stuff<BR>
[19:59:49] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Because the autoconf/automake stuff kind of uses a workaround for how bad autoconf/automake is at handling dependencies in directories<BR>
[20:00:02] <font color="#7a40b0">exult-bridge:</font><font color="#005000">Marzo:</font> Namely, building static libraries for the directories<BR>
[20:14:05] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> I have no problem with going cmake (except for the usual ios xcode project thing) 🙂<BR>
[20:14:56] <font color="#7a40b0">exult-bridge:</font><font color="#600060">Dominus:</font> the vorbis rint thing surfaced here as well https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247799 and some problem of libtool losing the -lm dependency_lib. If that makes sense to you<BR>