You describe the expected current behavior, I think. In the default freetype-demo way of building, after build, before install, "bin/xxx" is a libtool script which loads the binaries within "bin/.libs/" with LD_LIBRARY_PATH set to dynamically load the latest freetype shared library from "../freetype/src/.libs" . If you run the binaries in "bin/.libs" directly, you pick up your older system-wide freetype shared library instead. There is probably no reason for running bin/.libs directly though by-passing the libtool script, unless you are trying to generate statically linked binaries to the latest freetype - which I'll describe further below.
If the current behavior isn't what you want, you could either do "make install" to install to a location of your choice (after setting --prefix appropriately) both the latest binaries and the latest shared library; alternatively disable shared library building in ./configure'ing freetype. With the latter, "bin/xxx" would be statically linked binaries instead of libtool scripts, and there would be no "bin/.libs" sub-directories. I might be somewhat inaccurate in some of the description above, but I think that covers how I knows it works. Message: 1 Date: Mon, 28 Nov 2016 16:24:55 +0100 From: Florian Willich <[email protected]> To: [email protected] Subject: [ft-devel] ftview version output issue Dear Freetype Developers, compiling the ftdemo of version 2.7 as described in the readmes I have the following issue: Executing the following command in ../bin/ $ ./ftview -v Outputs: ftview (FreeType) 2.7 Executing the same command in ../bin/.libs/ Outputs: ftview (FreeType) 2.6.3 Do you know if I just compiled something wrong? Or is the ftview wrapper script outputting the correct version and the executable not? Kind regards, Flo _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
