normally if i am building something that requires NEWER versiond of software than are in the OS's repos
i build it and ALL of it's dependencies out of the system $PATH
darktable should build just like i do for gimp 2.9 development
i build it in my
/home/userName/bin/SourceFolder
and install it to
/home/userName/bin/ProgramNameFolder
and use a "config.site" file in
/home/userName/bin/ProgramNameFolder/share
the text file that is
/home/userName/bin/ProgramNameFolder/share/config.site
has the build variables to be exported to autotools
-- an example for my gimp2.9.4 build
Code:
export PATH="/home/johnvv/bin/Gimp/bin:$PATH"
export PKG_CONFIG_PATH="/home/johnvv/bin/Gimp/lib64/pkgconfig:$PKG_CONFIG_PATH"
export LD_LIBRARY_PATH="/home/johnvv/bin/Gimp/lib64:$LD_LIBRARY_PATH"
export ACLOCAL_FLAGS="-I /home/johnvv/bin/Gimp/share/aclocal $ACLOCAL_FLAGS"
export XDG_DATA_DIRS="/home/johnvv/bin/Gimp/share:$XDG_DATA_DIRS"
i build that and a newer libpng in the gimp install location
you can do the same thing for darktable on Cent7
have a read through the gimp dev build wiki
( gimp is a GREAT TOOL to use for examples do to the MASSIVE DOCUMENTATION )
http://wiki.gimp.org/wiki/Hacking:Building/Linux
just port the instructions for use with darktable
for the config.site use google and gnu
-- old but usable
https://www.gnu.org/software/automak..._002esite.html