[ptx] libpano12 - build with GNU autoconf, automake and libtool

[Andreas Hirczy]

Bruno Postle <bruno at postle.net> writes:

> Everything works fine for me on fedora fc2, these are my comments so
> far:
> 
> - Java libraries.  The pano12 library can be built without Sun Java,
>   as long as you have gnu gcc-gcj headers in place.
> 
> - The header files are being installed to $PREFIX/include.  Hugin
>   and other tools expect them in $PREFIX/include/pano12 - This is
>   probably why you can't get hugin to build.

I am also writing some debian code and call configure with --includedir=...;
I have changed ./bootstrap to reflect this. Are all programms expecting
libpano12 header files in pano12/?

I have seen your second post on missing header files in the distribution
(makefile.* is missing also), will look for a solution later.

> - Just five of the header files are installed by the Makefile, is
>   this intentional or are these all that are required to link to the
>   library?  This could be the other reason hugin doesn't build.

It seemed to me, only those header files will be read by other programs on
compilation. 

> - I don't have a full list of contributor names, but you should at
>   least add Bret McKee to the AUTHORS file.

Thanks.

> - This build system needs to work on mac osx and win32 as well as
>   linux.  We need testers for osx and Windows, any volunteers?

I will try it on MacOS X, but have not got much spare time this week - would
be nice if somebody else could step in. Sorry, no windows here :)

> - It was a mistake to introduce the old windows makefile into CVS as
>   'Makefile', this should be renamed to 'makefile.win32' so there is
>   no collision with the automake generated file.

> - These files and links are created:
> 
>     libpano12.so -> libpano12.so.0.0.0
>     libpano12.so.0 -> libpano12.so.0.0.0
>     libpano12.so.0.0.0
>         
>   I'm not sure, but shouldn't they be something like this:
> 
>     libpano12.so -> libpano12.so.2.7.0.7
>     libpano12.so.2 -> libpano12.so.2.7.0.7
>     libpano12.so.2.7.0.7

No - those numbers do not reflect version numbers for the source code, but
"library interface versions". There are always three numbers and each has its
own special meaning: <http://www.gnu.org/software/libtool/manual.html#SEC34>

> If nobody objects, I'll add the three new files (AUTHORS, bootstrap,
> configure.in, HACKING & Makefile.am) to the libpano CVS.

Go ahead, but I have a new bootstrap (--includedir) and AUTHORS (Bret McKee)
in <http://itp.tugraz.at/~ahi/download/libpano12-autotools-2004-11-08.tar>.


-- 
Andreas Hirczy <ahi at itp.tugraz.at>                   http://itp.tugraz.at/~ahi/
Graz University of Technology                          phone: +43/316/873-81 90
Institute of Theoretical and Computational Physics       fax: +43/316/873-86 78
Petersgasse 16, A-8010 Graz                         mobile: +43/699/19 14 24 60