freetype 2.5.1 fails to build universal under PPC Tiger

[t.tensi@…]

Dear all,
the universal build of the current freetype version 2.5.1 fails under Tiger with error

configure: error: `libpng-config' not found;
either set the LIBPNG_CFLAGS and LIBPNG_LDFLAGS environment variables,
or pass `--without-png' to the `configure' script.''

The fix is easy: I have added the recommended --without-png flag to the list of configure flags:

platform macosx {
  if {${os.major} < 9} {
    configure.args-append \
      --with-old-mac-fonts \
      --without-png
  }
}

Best regards,

Thomas

[ryandesign (Ryan Carsten Schmidt)]

I can't even get freetype's dependency bzip2 to build universal on Tiger, due to a different problem, so I'm not sure how you were even able to attempt a universal build of freetype on Tiger.

Universal building is more difficult on Tiger on PowerPC than it is on Tiger on Intel or on later OS X versions. I can try to fix these issues, but I question whether you really need to build anything universal on Tiger on PowerPC. The only reason to do so would be if you intend to build this software on your PowerPC Mac and then run it on an Intel Mac. Do you? If so, why can't you build it on the Intel Mac in the first place?

[t.tensi@…]

Dear Ryan,

thanks for your quick response! I am building on Tiger on an old G4 Mac Mini, because an elderly friend of mine is running that platform and I am providing some software for him. And I want to have a universal build "just in case" without owning an Intel Mac, because another friend has an Intel Mac.

You are right: bzip2 does not build universal out of the box on the Power PC. I have adapted the Portfile, because the canonical archflags did not seem to work.

...
set sysroot "-isysroot /Developer/SDKs/MacOSX10.4u.sdk"
build.args              CC="${configure.cc} ${sysroot} [get_canonical_archflag
s cc]" \
                          PREFIX=${prefix}
...

Sorry, I did not report this back to the maintainer.

I understand that supporting those really old platforms is not worthwhile, but I did not have any problems with freetype until the 2.5.1 version and it was easy to fix.

Best regards, Thomas