oitofelix wrote: ↑March 9th, 2017, 8:14 pmNorbert wrote: then if I run the program it says:
-----
./mininim: error while loading shared libraries: liballegro.so.5.2: cannot open shared object file: No such file or directory
-----
I could probably figure out what the problem is there (maybe a symbolic link would fix it), but I'm busy with other things.
Perhaps that's because you have your distribution's Allegro installed alongside MININIM's fork. Try
Code: Select all
sudo apt-get remove liballegro5-dev liballegro-image5-dev \
liballegro-audio5-dev liballegro-acodec5-dev liballegro-dialog5-dev
Then don't forget to run
.
It took me a while, but I've now tried this.
It doesn't fix the problem.
oitofelix wrote: ↑March 9th, 2017, 8:14 pmNorbert wrote:Regardless, if we both can't make it work out of the box with the available instructions, it needs work.
Well, there are an infinitude of possible configurations for GNU/Linux systems out there. This is life when it comes to building software. I can't possibly foresee every possible corner case in which the build procedure can fail. As experience shows, build recipes are just general guidance to point people
committed to the task of building from source to the right direction at best. There is absolutely no guarantee, implicit or otherwise, that they will work for you out of the box if you follow them rigorously. You should just consider yourself lucky, in case they do. That's not to say however that I won't help users building MININIM or that MININIM's building documentation can't be improved.
I may disagree with your stance here. I normally don't run into the kind of problems that I run into with MININIM when manually compiling packages. While there are a lot of possible configurations for GNU/Linux systems, my Mint installation is fairly standard, and the distro is part of the prominent group of Debian/Ubuntu-based systems; even relies on Ubuntu's repositories. I don't think your statement that you "can't possibly foresee every possible corner case" is applicable in this instance; also, I wouldn't ask (or expect) you to. My experience with manually compiling packages is not that one "should just consider yourself lucky, in case [instructions/building work(s)]". If I can't simply follow the instructions, even for a huge package such as Wine, then I'm unlucky.
There's something I've been meaning to ask you. The
page at GitHub about the 201701051749 release says "oitofelix released this on Dec 28, 2016". I can imagine you decided to push out this release earlier than expected, but I'm wondering why the version number that includes datetime 2017-01-05_17:49 wasn't changed to match the release date.
Anyway, today I wanted to test the legitimacy of the uploaded MININIM replays I linked to
here, saw you made some replay related commits on January 5th of 2017, and therefore opted to manually compile a recent MININIM. (Also, the Windows version crashes in my Wine.)
I decided to clone Allegro. Following MININIM's documentation, I tried...
Code: Select all
$ sudo apt-get build-dep allegro5
Reading package lists... Done
E: Unable to find a source package for allegro5
...which failed; as did cmake and make:
Code: Select all
$ cmake
Usage
cmake [options] <path-to-source>
cmake [options] <path-to-existing-build>
Specify a source directory to (re-)generate a build system for it in the
current working directory. Specify an existing build directory to
re-generate its build system.
Run 'cmake --help' for more information.
$ make
make: *** No targets specified and no makefile found. Stop.
I made progress with...
Code: Select all
mkdir build
cd build
cmake ..
make
...and (thus) later "cd ../..".
MININIM compiled, but, unfortunately, I ran into the same shared library error as I did in March:
Code: Select all
$ ./mininim
./mininim: error while loading shared libraries: liballegro.so.5.2: cannot open shared object file: No such file or directory
I decided to run...
Code: Select all
$ sudo xargs rm < allegro5/build/install_manifest.txt
$ sudo apt-get install liballegro5-dev
...and tried both 201701122309 and the bleeding edge master. Configure ended with:
Code: Select all
[...]
checking for ALLEGRO... no
checking for ALLEGRO... yes
checking for ALLEGRO_IMAGE... no
checking for ALLEGRO_IMAGE... no
configure: error: MININIM requires Allegro 5.0.9 (or superior) image addon
(Strange that it mentions both ALLEGRO and ALLEGRO_IMAGE twice, with the former saying "no" and then "yes".)
I have a suggestion here. I started checking...
Code: Select all
$ sudo dpkg -s liballegro5-dev|grep Version
Version: 2:5.0.11-2
...because the error message appears to address "Allegro 5.0.9".
The suggestion is to modify configure.ac to use:
Code: Select all
AC_MSG_ERROR([MININIM requires Allegro-image $allegro_minver (or superior)]))])
instead of:
Code: Select all
AC_MSG_ERROR([MININIM requires Allegro $allegro_minver (or superior) image addon]))])
The same goes for the messages about Allegro-audio, Allegro-acodec and Allegro-dialog.
But yeah, now make says ALLEGRO_MENU and such are unknown.
Oh well, 2.15am local time. Time for bed.