Re: First Compilation

On Thu, 2003-07-31 at 21:31, Mike Melanson wrote:
> Hi,
> 	Okay, I installed FreeType2 and have been fighting with the libstk
> build for a little while. It looks like I built the library. 12 megabytes?
> Wow, but it strips to 577 KB which is a bit better. 

Gotta love C++ debug symbols!  Still, that is larger than I thought...
guess its grown recently.

> Right now, I am trying to compile the samples.

One tip: make sure you have Arial.ttf in /usr/share/libstk/fonts

We need to find a free font we can distribute with libstk that gets
installed with make install and have the demos use that, but until
then...

> 	Is this someone's first experience using the autotools? There are
> some telltale signs, such as Makefiles lying around in different
> directories, not to mention libstk_old.tar.gz in the root, the removal of
> which would shrink the archive notably. When the autotools are set up
> properly, all that is required is a 'make dist' command in the main
> directory and the tools actually create the distribution tarball for you
> with all the necessary files (and only the necessary files).
> 

This is my first time using the autotools in a project of this scope.  I
admit to probably doing some things wrong.  I have started using
pkg-config to find the right location of libs/includes/etc, but haven't
gotten around to fixing freetype (you'll note that the Makefile.am has a
comment to fix the way we link to freetype).  Adding that to the TODO
also, that shouldn't be hard to fix, its just a matter of doing it. 
libstk_old is actually a prior version of the library, very old (read
not related to the current one), and can probably be removed now.

> 	My biggest problem in compiling the library was that FreeType2
> installed itself in /usr/local/include. libstk feels that FT2 should be in
> /usr/include, probably because that's what Debian dictates. libstk's
> configure script should automatically detect the correct include
> directories based on the output of 'freetype-config --cflags'. Eventually,
> I had to create a symbolic link from /usr/include/freetype2 ->
> /usr/local/include/freetype2 because I could not coerce libstk's build
> system to use the correct path.

Yup.  You are the first person (other than the 4 core developers) to try
and use this library, so I appreciate your patience.  Please keep me
posted of any other problems you run into.  I am also open to more
suggestions on what we can do to improve the build process.

Thanks,

Darren

> 
> 	I will continue to do battle with the demo programs. I want a
> baseline on my Linux machine before moving onto STK on DC.
> 
> --
> 	-Mike Melanson
> 
> 
> _______________________________________________
> Libstk mailing list
> [email protected]
> http://www.dvhart.com/cgi-bin/mailman/listinfo/libstk