Help installing Anti-Grain Geometry so gnash will work

Geraldsmod · 09-27-2009, 08:40 PM

I'm trying to install Anti-Grain Geometry so I can use gnash but I can't figure out how to install it. (Link here.)

I have to compile it from source because I use an unpopular distro.

What I've done so far:
Downloaded AGG v2.5 Linux Archive from here.
tar -xzf agg-2.5.tar.gz
cd ./agg-2.5
make
cd ./examples/X11
make clean
make

I don't know what to do next. Gnash is still saying I do not have AGG installed.

The install file reads:

Code:

Anti-Grain Geometry is a C++ library distributed in sources
and does not require any installation procedure. The source code 
is platform independent and does not have any dependencies on 
system APIs (except for very standard C runtime library).
You just take source files and include them into 
your project. The sources are maintained to be highly compatible
with most popular C++ compilers, including poor ones, like
Microsoft Visual C++ V6.0. 

On Unix/Linux/MacOS/BeOS/AmigaOS systems you can type "make" to 
build src/libagg.a There must be GNU Make utility installed.
Makefiles are very simple, so that if something goes wrong
you could easily fix it. There are no "include files" 
dependency suppoeted.
Also note that there's no "make install" option either;
basically the original Makefiles are needed only to build
the examples. 

After building the library you do "cd examples/<YourOS>" and build 
the examples in a similar way. 

On most Linux platforms the "automake" environment should work.
It's generously provided by Nikolas Zimmermann, aka WildFox,
who is a key developer of KDE and KSVG.
This process will replace the original Makefiles.

On Windows there's no library or a DLL created at all. You just
add source files into your project or create a preoject to build 
a LIB/DLL if you wish. The problem is that it's very tedious to 
maintain building environments for all possible configurations. 
I'm sorry for not automating it, but the compensation is that
AGG compiles fine without any hidden problems, nor the neccesity
to configure.
All examples have building environments for Microsoft Visual C++ 6.0
(.dsp/.dsw) and they are self-sufficient. The newer versions
of the studio can easily convert the projects.

Also, see "readme" for more details.

Can someone please help me?

{BBI}Nexus{BBI} · 09-27-2009, 09:15 PM

For the final stage you should switch to root (at the same location) then type: make install.

Geraldsmod · 09-27-2009, 09:21 PM

In the install file it says:

Code:

Also note that there's no "make install" option either;
basically the original Makefiles are needed only to build
the examples.

Geraldsmod · 09-28-2009, 03:50 PM

Does anyone know the right way to install this?

{BBI}Nexus{BBI} · 09-29-2009, 12:16 PM

Quote:

Originally Posted by Geraldsmod

Does anyone know the right way to install this?

There's nothing more for you to do re the installation of AGG. Perhaps this will help you to get it working:

Quote:

I've built the latest Gnash with the following
./configure --enable-renderer=agg --enable-gui=fb && make && make install

Source: http://osdir.com/ml/gnu.gnash.devel/.../msg00026.html

Quakeboy02 · 09-29-2009, 01:40 PM

What you have hopefully built is "libagg.a". If Nexus' comments don't help, try making a directory "agg" in your gnash source directory, and putting libagg.a there.

It would help A LOT if you would post the EXACT error message that gnash compile is giving. We can't see your screen. Otherwise, as you can see, we're just guessing.

Added:
Your long quote says there's a readme file. Did you read it?

H_TeXMeX_H · 09-29-2009, 02:51 PM

I say you forget about agg and use the opengl renderer, but it depends on your video card and drivers.

Geraldsmod · 09-29-2009, 04:42 PM

Well I tried Nexus's way and that still came back as this:

Code:

 ERROR: No AGG development package installed!
               Install it from http://www.antigrain.com
               or .deb users: apt-get install libagg-dev
               or .rpm users: yum install agg-devel
configure: error: Please install required packages

I cannot find a ligagg.a but there is an ligagg.m4 and ligagg.pc.in

I tried to build gnash with the sdl gui...
./configure --enable-renderer=opengl --enable-gui=sdl
and the gtk gui...
./configure --enable-renderer=opengl --enable-gui=gtk
and they both came with this output:

Code:

 WARNING: without --enable-docbook we will use the cached
                 documentation files included in the gnash distribution.
                 If you change files in doc/C, you should --enable-docbook.
        WARNING: You need to have the Ming development package
                 installed to run most of the tests in Gnash testsuite.
                 Install it from http://www.libming.org/
                 or .deb users: apt-get install libming-dev
        WARNING: You need to have the Ming utilities package
                 installed to run most of the tests in Gnash testsuite.
                 Install it from http://www.libming.org
                 or .deb users: apt-get install libming-util
        WARNING: You need to have the MTASC compiler packages installed
                 to run some of the tests in Gnash testsuite.
                 You can install it from http://mtasc.org
                 or .deb users: apt-get install mtasc
        WARNING: You need to have the HAXE compiler package 
                 version 2.00 or higher installed
                 to run some of the tests in Gnash testsuite.
                 You can install it from http://haxe.org
                 or .deb users: apt-get install haxe
        WARNING: You need to have the 'swfmill' tool installed
                 to run some of the tests in Gnash testsuite.
                 You can install it from http://swfmill.org/
                 or .deb users: apt-get install swfmill
        WARNING: You need to have 'swfc' from SWFTools installed
                 to run some of the tests in Gnash testsuite.
                 You can install it from http://www.swftools.org/
                 or .deb users: apt-get install swftools
        WARNING: you need as3compile from SWFTools
                 to run some of the tests in Gnash testsuite.
                 You can install it from http://www.swftools.org/
        WARNING: You need to have csound installed
                 to have real fun.
                 Install it from http://www.csounds.com/
                 or .deb users: apt-get install csound
                 or .rpm users: yum install csound
        WARNING: You need the dejagnu package installed to get a summary
                 report after running ''make check''
                 Install it from http://www.gnu.org/software/dejagnu/
                 or .deb users: apt-get install dejagnu
                 or .rpm users: yum install dejagnu

Gnash should still compile even with these warnings.
If it doesn't, report the warnings as a bug.

I wish there was an easy way to install agg... And yes I read the readme also. It says:

Code:

Use automake to build the library.

If automake is not available you still can use the old make.
There is a very simple Makefile that can be used. Note that
if you use automake it will overwrite Makefile.

---------------------------------

If building on AmigaOS 4.0 or higher type the following for
instructions on what targets are available.
 make -f Makefile.AmigaOS

To just build and install AGG into the standard AmigaOS SDK
ready for use type:
 make -f Makefile.AmigaOS install

If you just want to build one demo (e.g. lion) use:
 make -f Makefile.AmigaOS bin/lion

If you have any questions about the AmigaOS port please
contact Steven Solie (ssolie@telus.net) for help.

---------------------------------

To build all examples using SDL (Mac or Linux) just type:

cd /examples/sdl
make

Individual examples can be built with

make aa_test

In the same way the native Carbon examples can be built with

cd /examples/macosx_carbon
make

In both cases the static library will be built (if it was not already) 
from the existing global Makefile in /src/.

The Makefiles for both SDL and Carbon will also attempt to download the 
required .bmp files if they are not found in the system for a given 
example. If the files could not be fetched (wget) the user will receive 
a message explaining where to download the samples from (sphere.bmp, 
etc.)  Since all programs reside in the same directory there is no need 
to duplicate the .bmp files for each program that needs to use them.

Then if I try to automake agg it outputs at the end:

Code:

Makefile.am: required file `./INSTALL' not found
Makefile.am:   `automake --add-missing' can install `INSTALL'
Makefile.am: required file `./NEWS' not found
Makefile.am: required file `./README' not found
Makefile.am: required file `./AUTHORS' not found
Makefile.am: required file `./COPYING' not found
Makefile.am:   `automake --add-missing' can install `COPYING'

If I rename all of those files to capital letters like they're supposed to be then it outputs:

Code:

configure.in: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.in: You should verify that configure.in invokes AM_INIT_AUTOMAKE,
configure.in: that aclocal.m4 is present in the top-level directory,
configure.in: and that aclocal.m4 was recently regenerated (using aclocal).
configure.in:2: required file `./config.guess' not found
configure.in:2:   `automake --add-missing' can install `config.guess'
configure.in:2: required file `./config.sub' not found
configure.in:2:   `automake --add-missing' can install `config.sub'
configure.in:16: required file `./install-sh' not found
configure.in:16:   `automake --add-missing' can install `install-sh'
examples/Makefile.am:3: ENABLE_EXAMPLES does not appear in AM_CONDITIONAL
examples/Makefile.am:5: ENABLE_WIN32_TT does not appear in AM_CONDITIONAL
examples/Makefile.am:9: ENABLE_FT does not appear in AM_CONDITIONAL
examples/Makefile.am:13: ENABLE_GPC does not appear in AM_CONDITIONAL
examples/Makefile.am:19: Libtool library used but `LIBTOOL' is undefined
examples/Makefile.am:19:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
examples/Makefile.am:19:   to `configure.in' and run `aclocal' and `autoconf' again.
examples/Makefile.am:19:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
examples/Makefile.am:19:   its definition is in aclocal's search path.
examples/Makefile.am: required file `./depcomp' not found
examples/Makefile.am:   `automake --add-missing' can install `depcomp'
/usr/share/automake-1.11/am/depend2.am: am__fastdepCXX does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `am__fastdepCXX' is to add `AC_PROG_CXX'
/usr/share/automake-1.11/am/depend2.am:   to `configure.in' and run `aclocal' and `autoconf' again.
/usr/share/automake-1.11/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `AMDEP' is to add one of the compiler tests
/usr/share/automake-1.11/am/depend2.am:     AC_PROG_CC, AC_PROG_CXX, AC_PROG_CXX, AC_PROG_OBJC,
/usr/share/automake-1.11/am/depend2.am:     AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.11/am/depend2.am:   to `configure.in' and run `aclocal' and `autoconf' again.
examples/Makefile.am:222: variable `trans_curve2_ft_SOURCES' is defined but no program or
examples/Makefile.am:222: library has `trans_curve2_ft' as canonical name (possible typo)
examples/Makefile.am:227: variable `trans_curve1_ft_SOURCES' is defined but no program or
examples/Makefile.am:227: library has `trans_curve1_ft' as canonical name (possible typo)
examples/Makefile.am:224: variable `trans_curve2_ft_LDFLAGS' is defined but no program or
examples/Makefile.am:224: library has `trans_curve2_ft' as canonical name (possible typo)
examples/Makefile.am:229: variable `trans_curve1_ft_LDFLAGS' is defined but no program or
examples/Makefile.am:229: library has `trans_curve1_ft' as canonical name (possible typo)
font_freetype/Makefile.am:2: ENABLE_FT does not appear in AM_CONDITIONAL
font_freetype/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
font_freetype/Makefile.am:5:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
font_freetype/Makefile.am:5:   to `configure.in' and run `aclocal' and `autoconf' again.
font_freetype/Makefile.am:5:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
font_freetype/Makefile.am:5:   its definition is in aclocal's search path.
font_win32_tt/Makefile.am:4: ENABLE_WIN32_TT does not appear in AM_CONDITIONAL
font_win32_tt/Makefile.am:7: Libtool library used but `LIBTOOL' is undefined
font_win32_tt/Makefile.am:7:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
font_win32_tt/Makefile.am:7:   to `configure.in' and run `aclocal' and `autoconf' again.
font_win32_tt/Makefile.am:7:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
font_win32_tt/Makefile.am:7:   its definition is in aclocal's search path.
gpc/Makefile.am:1: ENABLE_GPC does not appear in AM_CONDITIONAL
gpc/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
gpc/Makefile.am:2:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
gpc/Makefile.am:2:   to `configure.in' and run `aclocal' and `autoconf' again.
gpc/Makefile.am:2:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
gpc/Makefile.am:2:   its definition is in aclocal's search path.
/usr/share/automake-1.11/am/depend2.am: am__fastdepCC does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `am__fastdepCC' is to add `AC_PROG_CC'
/usr/share/automake-1.11/am/depend2.am:   to `configure.in' and run `aclocal' and `autoconf' again.
configure.in:3: required file `include/config.h.in' not found
src/Makefile.am:34: ENABLE_GPC does not appear in AM_CONDITIONAL
src/Makefile.am:40: ENABLE_CTRL does not appear in AM_CONDITIONAL
src/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:5:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:5:   to `configure.in' and run `aclocal' and `autoconf' again.
src/Makefile.am:5:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/Makefile.am:5:   its definition is in aclocal's search path.
src/ctrl/Makefile.am:1: ENABLE_CTRL does not appear in AM_CONDITIONAL
src/ctrl/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/ctrl/Makefile.am:4:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/ctrl/Makefile.am:4:   to `configure.in' and run `aclocal' and `autoconf' again.
src/ctrl/Makefile.am:4:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/ctrl/Makefile.am:4:   its definition is in aclocal's search path.
src/platform/X11/Makefile.am:1: ENABLE_X11 does not appear in AM_CONDITIONAL
src/platform/X11/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
src/platform/X11/Makefile.am:2:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/platform/X11/Makefile.am:2:   to `configure.in' and run `aclocal' and `autoconf' again.
src/platform/X11/Makefile.am:2:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/platform/X11/Makefile.am:2:   its definition is in aclocal's search path.
src/platform/mac/Makefile.am:1: ENABLE_OSX does not appear in AM_CONDITIONAL
src/platform/mac/Makefile.am:2: Libtool library used but `LIBTOOL' is undefined
src/platform/mac/Makefile.am:2:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/platform/mac/Makefile.am:2:   to `configure.in' and run `aclocal' and `autoconf' again.
src/platform/mac/Makefile.am:2:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/platform/mac/Makefile.am:2:   its definition is in aclocal's search path.
src/platform/sdl/Makefile.am:1: ENABLE_SDL does not appear in AM_CONDITIONAL
src/platform/sdl/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined
src/platform/sdl/Makefile.am:3:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/platform/sdl/Makefile.am:3:   to `configure.in' and run `aclocal' and `autoconf' again.
src/platform/sdl/Makefile.am:3:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/platform/sdl/Makefile.am:3:   its definition is in aclocal's search path.
src/platform/win32/Makefile.am:3: ENABLE_WIN32 does not appear in AM_CONDITIONAL
src/platform/win32/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/platform/win32/Makefile.am:4:   The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/platform/win32/Makefile.am:4:   to `configure.in' and run `aclocal' and `autoconf' again.
src/platform/win32/Makefile.am:4:   If `AC_PROG_LIBTOOL' is in `configure.in', make sure
src/platform/win32/Makefile.am:4:   its definition is in aclocal's search path.

It looks like required files are missing but I got the tarball from the AGG website...

{BBI}Nexus{BBI} · 09-29-2009, 05:10 PM

The solution to resolving the error is given

Quote:

or .deb users: apt-get install libagg-dev

Run that from the commandline:sudo apt-get install libagg-dev or use Synaptic package manager to install it, then compile Gnash again.

Quakeboy02 · 09-29-2009, 05:21 PM

OK, I downloaded libagg-dev to my Debian machine, and looked at the files that were installed.

First: There were a number of files placed in /usr/lib. As you can see, these are files ending in ".a". Those files should have been created when you did the make in the "src" directory. All you should need to do is add that directory to your linkage list.

Code:

/usr/lib/libagg.a
/usr/lib/libaggplatformX11.a
/usr/lib/libaggplatformsdl.a
/usr/lib/libaggfontfreetype.a
/usr/lib/pkgconfig
/usr/lib/pkgconfig/libagg.pc
/usr/lib/libaggfontfreetype_pic.a
/usr/lib/libaggplatformsdl_pic.a
/usr/lib/libaggplatformX11_pic.a
/usr/lib/libagg_pic.a

Second: There is a long list of files in "/usr/include/agg2", which only makes sense. If you will add the directory in the libagg source tree that has the header files to your makefile, then that should resolve the compile part of the problem.

Unwanted advice follows:
Strongly consider switching distros to a more mainline one that installs complete pre-compiled packages for you. Failing that, you need to just learn more about how to compile and install packages in Linux. I use Debian, there are others...

Geraldsmod · 09-29-2009, 05:32 PM

Okay finally! I have an libagg.a
This file is found in /home/user/Downloads/agg-2.5/src and my gnash folder is in /home/user/gnash-0.8.6

There is nothing in /usr/lib regarging agg though.
How should I go about making gnash recognize that I have agg installed?

Also, I don't want to go to a mainline distro because I want a disto that is entirely 100% free software. Unfortunately, there are no free mainline distros.

Quakeboy02 · 09-29-2009, 06:12 PM

I guess I kinda/sorta understand your desire to have 100% free software, but you do understand that this puts a pretty big burden on you, right? If you're using Slackware, you might want to joint the Slack forum here, on LQ to get better support for the Slack-related issues. There is also a Linux From Scratch forum that might give you some good help on questions of this type.

But, back to your problem. I still think you have two separate issues. One is that the compiler doesn't know where your libagg header files are. You will probably have to add this in with a "-I" (include) switch to the makefile, if memory serves. It needs to point to the directory in the libagg package where the header files (*.h) are. Or you could maybe copy them to /usr/include, like I suggested above, or add a symlink. Once the source compiles, you'll need to deal with the linkage problem. That is probably done by adding a "-L' switch to the makefile.

Sorry I can't give you more direct help, but it's been a decade since I did this sort of stuff. Maybe now that the problem is better defined someone else can correct the above.