Compiling splashy pkg-config problem
 

I am getting this error trying to configure splashy

If I try ./configure PKG_CONFIG=/usr/lib/pkgconfig

So where is the pkg-config script? There is a /usr/lib/pkgconfig directory full of *.pc files.

Hm, I built splashy on my Slackware 12.0 last week, and did not see this error.
What you do need is - directfb >= 0.9.22 (but I saw you built 1.0.0 already), glib2, freetype and all of those with static libraries (my freetype package has this and I can upload a modified glib2 package with SlackBuild and static libs if you want).
You need to build a static binary of splashy so that it can be used inside a initrd (if you want that).

Eric

I have just gone into my Slackware 12 installation and it configured fine.
It did not make because of

So presumably I need to sort out glib2 and freetype there (though I thought I had them installed)

Anyway I am still using Slackware 11 as my working distro and would like to get it sorted there. It seems that there is a file /usr/bin/pkg-config which I have in 12 but not in 11. Is it possible that pkgconfig needs upgrading?

BTW I edited your directfb.slackbuild

It turns out that I did not have pkg-config installed on 11. I cannot understand why. Anyway it is there now and I have libglib to sort out

I am wondering if this is more trouble than it is worth. I have glib2-2-10.3 - presumably the original slackware 11 package. Do I have to replace this with a different glib2? Does this have any downside?

You will have to recompile glib2 and freetype, and recompile directfb, to generate static libraries (*.a files).
This does not harm your Slackware installation at all. Pat does not inlude static libraries because they mean additional MB's on the CD and on your hard disk, and Slackware uses dynamic libraries wherever possible to save space (and RAM!).
Programs that operate in an initrd and in the early stages of boot often are statically compiled because you can never be sure that all the libraries in /usr/lib are already available to the program (for instance if /usr is on a separate partition and not yet mounted).

Eric

Well in that case I would appreciate your glib2 slackpackage.

Can I assume that I do not need to recompile directfb if I did it using your slackbuild?

Here's a funny thing. When I downloaded your slackbuild files by right-clicking and 'Save as' in Firefox the slack-desc file was saved as slack-desc.htm which broke the build. I had to rename the file.

Actually I do not think I need your package. I have edited Pat's package to compile with static libraries.

Well I have two penguins at boot as I should but I am not sure if this means that splashy is working

You will have to add commands for splashy to show anything during boot-up.
You will need to edit rc.S and rc.M at least to show the initial splash screen and to add progress indicators.
If you want a bootsplash very early in the boot you will have to add commands to an initrd as well, as well as add the splashy binary into the initrd image.

There is another thread from last week which describes the process if I remember correctly.

Eric

Well I do not think I even have it configured yet.

There is no /etc/splashy