LinuxQuestions.org - [SOLVED] Building from source: Dependencies and PKG_CONFIG

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Building from source: Dependencies and PKG_CONFIG_PATH (https://www.linuxquestions.org/questions/slackware-14/building-from-source-dependencies-and-pkg_config_path-946597/)

Building from source: Dependencies and PKG_CONFIG_PATH

I've been reading various SlackBuilds lately, and one of those was the official Xfce SlackBuild. Slackware's Xfce is some sort of an "all-in-one" package; it contains libxfce4util, xfconf, xfceutils, thunar etc. So, my questions is this:

Considering that xfconf, for instance, depends on libxfce4util, how come the SlackBuild doesn't fail? I mean libxfe4util is compiled and installed in a non-standard place (/tmp/package-xfce-4.62/libxfce4util-$VERSION/), and when the SlackBuild proceeds with the next module, xfconf, the dependency is satisfied and the SlackBuild doesn't fail.

But when I manually compile the modules, one by one, xfconf won't see libxfce4util, unless I actually install it on my system (/usr). The ./configure step will exit with an error about not finding the required package and making a suggestion about adjusting my PKG_CONFIG_PATH variable.

I guess you missed the line

Code:

make install || exit 1

in the SlackBuild? Every component is installed to the filesystem as well as to /tmp/package-xfce-4.62/libxfce4util-$VERSION/ .

Eric

OMG... I read the script 4 times or something and never saw this:

Code:

make $NUMJOBS || make || exit 1

make install || exit 1

make install DESTDIR=$PKG

Thanks Eric