Missing freetype2 headers, the freetype-config tool and its pkg-config files are missing.

[scottmc]

Splitting this off from #1739 as it grew from the discussion. Freetype2 is part of Haiku, but the freetype2 headers, the freetype-config tool and its pkg-config files are missing. This makes it difficult to port things to Haiku that rely on the system having those in place. They don't need to be part of Haiku, but should at least be available as an optional package or part of the development package.

[scottmc]

This looks to be partially fixed in r28570, but still need the the config tool and pkg-config to be added.

[anevilyak]

(In #3167) Thanks for the note!

[scottmc]

I've built and posted a freetype-2.3.7 binary for Haiku over on HaikuPorts, this package includes thee freetype2 headers, freetype-config tool and pkg-config files. So this could either be added as an optional package or the files can be pulled out of the binary zip and put into svn where needed. Once that is done this ticket can be closed out.

[korli]

It's just the config tool and pkg-config should be tuned with /boot/develop/headers and /boot/develop/lib

[scottmc]

I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick.  http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1

[bonefish]

Replying to scottmc:

I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick.  http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1

Maybe that's different for freetype, but usually "--libdir" specifies the installation directory for libraries.

[korli]

Replying to scottmc:

I've taken another look at this one and seems using --libdir=/boot/develop/headers/3rdparty during ./configure does the trick.  http://ports.haiku-files.org/wiki/media-libs/freetype/2.3.9/1

bonefish is right, you might try using --includedir=/boot/develop/headers/3rdparty instead.

[scottmc]

corrected.. i've updated the haikuports portlog entry to reflect this.

[korli]

I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ?

[bonefish]

Replying to korli:

I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ?

Nope, that isn't a prefix path, anyway.

[korli]

Replying to bonefish:

Replying to korli:

I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ?

Nope, that isn't a prefix path, anyway.

Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ?

[bonefish]

Replying to korli:

Replying to bonefish:

Replying to korli:

I added freetype-config in r30904. Should we use /boot/develop/abi/current for the prefix directory to be generic ?

Nope, that isn't a prefix path, anyway.

Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ?

I'm not quite sure, what the script is supposed to return. If it is the path for the linker, it should be /boot/develop/lib/x86 (for x86) or more generally /boot/develop/abi/current/lib. If it is the path where the library is located at runtime, it would be /system/lib.

Other then that, I think the prefix in the script is incorrect anyway, since with don't install freetype in /boot/common, but in /system.

[korli]

Replying to bonefish:

Libs reside in /boot/develop/lib/x86/. Should we then customize the script with the arch ?

I'm not quite sure, what the script is supposed to return. If it is the path for the linker, it should be /boot/develop/lib/x86 (for x86) or more generally /boot/develop/abi/current/lib. If it is the path where the library is located at runtime, it would be /system/lib.

When used with --libs, it's supposed to return how to link : -L/boot/develop/lib/x86 -lfreetype -lz For the time being, we could use /boot/develop/abi/current/lib then.

Other then that, I think the prefix in the script is incorrect anyway, since with don't install freetype in /boot/common, but in /system.

Agreed, I committed it as is to have an initial version. I suppose in a Linux environment, runtime and link libraries are at the same place.

[scottmc]

Is there anything left to do on this one? Freetype-2.3.11 is out now... Have the correct locations been ironed out yet?

[scottmc]

I've updated the pathnames in freetype-config in r33649, and updated freetype in r33650, then built and tried building of sdl-ttf and it checked for both freetype-config and pkg-config and was happy to just find the freetype-config. I suspect in most cases packages will do this, that is check for both and if they find one will be happy with it. So unless there's a need for the pkg-config I'm ok with leaving it out and closing this ticket as fixed. The paths may (or may not) need adjusting if/when the time comes for addressing the arch issues listed above.