How-to solve runpath-errors when splitting packages?

[Hartmut Goebel <h.goebel@crazy-compilers.com>]

Hi,

I'm currently packaging zbar (a bar-code scanner suite). zbar includes
"generic" binaries as well as "qt" anf "gtk" ones (zbarcam, zbarcam-qt,
zbarcam-gtk). I want to avoid having qt or gtk or even both as a
dependency of the `zbar` packages, as these would pull in *huge*
dependencies.

I already managed to split the output into several. Here is an the
file-list for zbar:qt:

/gnu/store/…-zbar-0.22-gtk/bin/zbarcam-gtk
/gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.so.0.0.2
/gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.a
/gnu/store/…-zbar-0.22-gtk/lib/libzbargtk.la
/gnu/store/…-zbar-0.22-gtk/include/zbar/zbargtk.h
/gnu/store/…-zbar-0.22-gtk/lib/pkgconfig/zbar-gtk.pc

Obviously zbarcam-gtk should use libzbargtk.so from the same output.

How can I make zbarcam-gtk find the lib? Any ideas?

I already tried:

0) Nothing special: phase "validate-runpath" fails.

1) Setting "#:validate-runpath? #f": build passes, but the program does
not find the lib.

2) Passing the equivalent of "LDFLAGS=-Wl,-rpath=${out_gtk}/lib
-Wl,-rpath=${out_qt}/lib" to configure. This leads to some "recursive
dependency error".

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |