Building EE for Windows just became a bit easier.
in EmptyEpsilon
Assuming you have a linux machine that is. Anything based on debian.
Also, the Windows Linux Subsystem will most likely work. But did not try that.
Instructions:
I hope I can manage the same for the Android build now.
Also, the Windows Linux Subsystem will most likely work. But did not try that.
Instructions:
sudo apt install mingw-w64 cmake
git clone https://github.com/daid/EmptyEpsilon.git
git clone https://github.com/daid/SeriousProton.git
cd EmptyEpsilon
mkdir _build_win32
cd _build_win32
cmake .. -DCMAKE_TOOLCHAIN_FILE=../cmake/mingw.toolchain -DSERIOUS_PROTON_DIR=../../SeriousProton
make -j 8 package
This should download and build SFML as well.I hope I can manage the same for the Android build now.
Comments
But making some progress.
Your kung fu is powerful.
https://github.com/daid/EmptyEpsilon/blob/master/android/Readme.md
I think it will work as a client just fine, but didn't test that yet.
Latest test version can also be found at http://daid.eu/ee/EmptyEpsilon.apk
I have tried the windows cross-compile, but sadly ran into issues.
Downloadling sfml, Compiling and creating the exe seems to work fine, however the packaging don't work.
There are a lot of errors about missing dll files in the form of
file INSTALL cannot find "/home/$USER/source/EmptyEpsilon/cmake/_win32//SFML_install/bin/libFLAC-8.dll".
There are similar other error messages for a couple of DLLs.
The strange thing is that the cmake says the linking of those dll worked (but in a strange path, "../../../lib", that does not exist and would be outside of the EE directory tree) however, I don't find them anywhere. Also, I don't see a folder "SFML_install", but the "//" indicates a Path error anyway.
The android bugs are expected, nothing has been done to fix those. But good to hear that it does something :-)
I now have the linux, android and windows builds running in CI, so I know if things fail to build again.
went pretty smooth. the first attempts produced errors both in the
cmake
command and in themake
command, for inability to copy some files. after a few attempts I addedsudo
to both these commands and it works great.my script also uses
$(grep -c ^processor /proc/cpuinfo)
instead of8
for CPU count.I do a lot of crosscompiling for my day job. So this is pretty much standard stuff for me.
Never tried gui applications in WLS
WLS is only intended for command line applications.
Then configuring and building ran fine for a while, although it complained about not finding ~/.android/repositories.cfg, which don't stopped it from building though.
The make part throwed a bunch of warnings, but did go quite far anyways, then it stopped with this output (rough translation, as it is german here)
-DDRMINGW_ROOT="../../drmingw-0.8.2-win32" -DENABLE_CRASH_LOGGER=1
in the cmake command, but I get a any idea what i'm doing wrong?Fact that you got to signing means that the build is pretty much done.
@greenshade I think the DRMINGW_ROOT needs to be an absolute path, at least. That's the difference I see with my build. But I hope to intigrade this into the whole auto-setup-and-build as well, so it is less error prone.
$(pwd)/../../drmingw-0.8.2-win32
and it works.I can haz crash logz now