Page 3 of 4
Re: Help Test portable Linux Love2d Binary
Posted: Fri Nov 11, 2016 7:09 am
by pacninja
Tested with love-0.10.2-amd64.tar.gz on Skylake iGPU and Debian Stretch.
It does launch but says ldconfig isn't found.
Code: Select all
# Distro
$ cat /etc/*-release
PRETTY_NAME="Debian GNU/Linux stretch/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (stretch)
Release: testing
Codename: stretch
# Graphics card
$ uname -mrs
Linux 4.6.0-1-amd64 x86_64
$ cat /proc/version
Linux version 4.6.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06)
$ glxinfo | grep "OpenGL renderer string"
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)
$ glxinfo | grep "OpenGL vendor"
OpenGL vendor string: Intel Open Source Technology Center
# Launch
$ ./love
./love: 4: ./love: ldconfig: not found
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 8:22 am
by easy82
Hello guys!
What is the status on this one?
I like the idea of AppImages, but this solution seems easier.
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 10:36 am
by bartbes
Not too much has happened since, though I have been able to turn the tarball into a snap, an AppImage and a flatpak.
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 11:01 am
by easy82
bartbes wrote:Not too much has happened since, though I have been able to turn the tarball into a snap, an AppImage and a flatpak.
Thanks for the info!
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 1:15 pm
by Fenrir
Is the 32bit version still planned? And I'm super interested by the AppImage version too!
Btw what's the plan with this, make it available on the Game Distribution wiki page?
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 1:27 pm
by bartbes
That's a good point. I've attached the new formats, so people can test those too. Next, I want to make it easier for everyone to build their fused games using this, then do a 32-bit build (though everyone should be using a 64-bit os these days...). And then.. I'll probably put the portable binaries up for download and link the scripts I use to build everything on Game Distribution, I guess.
EDIT: Btw, for those new to flatpak (I know I was), you can supposedly install the file using 'flatpak install --bundle <filename>', but you'll need to install the dependency, org.freedesktop.Platform, yourself.
Re: Help Test portable Linux Love2d Binary
Posted: Thu Dec 15, 2016 3:40 pm
by pgimeno
bartbes wrote:(though everyone should be using a 64-bit os these days...)
I promise I'll do before 2038!
Seriously though, I'm waiting for the next Debian release. Until then, I will only be able test when there are 32 bit binaries, or on occasion, using a borrowed 64-bit machine, but that's slower.
Re: Help Test portable Linux Love2d Binary
Posted: Mon Jan 23, 2017 9:27 am
by Fenrir
Hi guys,
I'm planning to use those binaries to distribute the Linux version of the game, is it OK? Is there any licence on the files I should be aware of?
Re: Help Test portable Linux Love2d Binary
Posted: Mon Jan 23, 2017 6:29 pm
by bartbes
As far as I'm concerned compilation isn't a creative work, so I assert no copyright on the binaries themselves
.
Seriously, though, the licensing situation is exactly the same as the windows binaries, except libstdc++ which is.. weird.
IANAL but I think you are allowed to redistribute libstdc++ along with closed-source programs (see also
this FSF page).
Otherwise, you can just remove libstdc++, only slightly reducing portability in the process.
Re: Help Test portable Linux Love2d Binary
Posted: Tue Jan 24, 2017 8:43 am
by Fenrir
OK thanks! Actually I was also thinking about the script file launching the executable.
About libstdc++, it's probably not a problem I think.