On Saturday 04 August 2007 19:01, snowcrash+bacula wrote: > > but it is *very* unusual for an application to do so. > > hm. well, we'll have to agree to disagree, then. > > *no* other f/oss app on my box -- and i build lots (admittedly, /not/ > Qt-based) -- currently has this problem. > > even bacula's "own" wx-console, when config's with: > > ... > --enable-bwx-console > ... > enable-bwx-console: yes wxWidgets 2.8 > > manages to 'get it right', properly finding the libs and generating > the correct prefix path > > cd bacula/src/wx-console/bwx-console.app/Contents/MacOS > otool -L bwx-console | grep wx > bwx-console: > /usr/local/wx284_dyn/lib/libwx_macu-2.8.0.dylib > (compatibility version 2.0.0, current version 2.1.0)
You are comparing apples and oranges. All the other Bacula consoles use *standard* libaries loaded in standard places or if they are installed in subdirectories, the installation process defines symbolic links from the standard libaries. qwt apparently doesn't load into a standard location on your machine, or the authors never thought to define symbolic links during the install process. > > > That's not due to the "OS" doing something right. It's also not due > to "Wx-Config" doing something right. No wx-config does nothing at execution time ... > > Rather, it's due to the bacula src correctly utilizing available > wx-config on this OS. > > My $0.02. If folks here don't think it needs fixin', then ok. *i* > have a workaround. > > 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
