> In general as long as you install the shared objects in one of the standard
> system libary files, all will work. Otherwise, you need to fiddle with the
> loader to tell it where to look for the binaries.
agreed, of course, in general.
in the case of bacula, though, i'd simply suggest that /especially/
given config of:
...
--with-qwt=/usr/local/qwt-5.0.2
...
bat support: yes -L/usr/local/qwt-5.0.2/lib
...
(btw, /usr/local/qwt-5.0.2 is the --prefix where qwt installs itself
*by default*; yes, that can be changed ...)
i'd simply propose that the bacula config/build has the info it needs
-- being aware of where the qwt libs are.
it can certainly, also, detect that the existing libs are dynamic
(.dylib), and the paths can be correctly generated.
in principle.
i have this nagging, unfounded suspicion, though, that this is a Qt issue ...
either way, the info's "there" ...
of course, as above, it can be manually worked around for now.
cheers!
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
