Status: open Group: Next Release (example) Created: Fri Mar 01, 2019 01:18 AM UTC by Joao ERIBERTO Mota Filho Last Updated: Fri Mar 01, 2019 01:18 AM UTC Owner: nobody
Hi Giuseppe,
The autogen.sh is calling for configure.in and libtool instead of
configure.ac and libtoolize.
The main goal of autogen.sh is generate basic files as configure and Makefile.in. Is a bad ideia provide theses files to final user inside your tarball because they must be generated by local system to be always updated. The autogen.sh should be simple and not test for commands presence (the Bash or a shell will tell us about absent commands). IMHO, I think that you can describe in README file the executables to be installed before run ./autogen.sh. It will avoid issues between Linux distributions across the time. You can use this:
The main goal of autogen.sh is generate basic files as configure and Makefile.in. Is a bad ideia provide theses files to final user inside your tarball because they must be generated by local system to be always updated. The autogen.sh should be simple and not test for commands presence (the Bash or a shell will tell us about absent commands). IMHO, I think that you can describe in README file the executables to be installed before run ./autogen.sh. It will avoid issues between Linux distributions across the time. You can use this:
Install libgtk2.0 and intltool.
Run the following commands:
$ ./autogen.sh
$ ./configure
$ make
make install
To cleanup the environment, some autogenerated files should be removed and 'make distclean' command fiixed.
The attached patch will fix all issues. However, to understand step by step, you can see all commits in my temporary repository here:
Status: open
Group: Next Release (example)
Created: Fri Mar 01, 2019 01:18 AM UTC by Joao ERIBERTO Mota Filho
Last Updated: Fri Mar 01, 2019 01:18 AM UTC
Owner: nobody
Hi Giuseppe,
The autogen.sh is calling for configure.in and libtool instead of configure.ac and libtoolize.
Hi Joao,
thanks a lot for your interest in Imagination. Do you know how to replace
it with an updated version?
Thanks
Giuseppe
On Fri, 1 Mar 2019 at 01:18, Joao ERIBERTO Mota Filho eriberto@users.sourceforge.net wrote:
Related
Feature Requests: #67
Hi Giuseppe,
The main goal of autogen.sh is generate basic files as configure and Makefile.in. Is a bad ideia provide theses files to final user inside your tarball because they must be generated by local system to be always updated. The autogen.sh should be simple and not test for commands presence (the Bash or a shell will tell us about absent commands). IMHO, I think that you can describe in README file the executables to be installed before run ./autogen.sh. It will avoid issues between Linux distributions across the time. You can use this:
The autogen.sh change will fix the following bug in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829985
To cleanup the environment, some autogenerated files should be removed and 'make distclean' command fixed.
The attached patch will fix all issues. However, to understand step by step, you can see all commits in my temporary repository here:
https://salsa.debian.org/eriberto/imagination-3.4-fixes/commits/master
Feel free to disagree with my changes and suggestions.
Cheers,
Eriberto
Last edit: Joao ERIBERTO Mota Filho 2019-03-02
Please, see the ticket in SF, I added an extra information. Thanks!
Em sex, 1 de mar de 2019 às 21:57, Joao ERIBERTO Mota Filho
eriberto@users.sourceforge.net escreveu:
Related
Feature Requests: #67