On Feb 6, 2015, at 12:32 PM, René J.V. Bertin <[email protected]> wrote:
> On Friday February 06 2015 11:23:05 Michael Jackson wrote: > >> I got around the issue by building zlib myself and installing to the >> "missing" path. This is at best a kludge and just really should not be >> needed. > > I don't know what kind of development you're doing, but it would be less of a > kludge to install MacPorts as it can really save one a lot of work installing > dependencies. I am doing pretty vanilla C++ development. We use Qt as our base for everything. We generate a GUI for data analysis which gets distributed to users, *not* developers. Those users do not have MacPorts on their systems. Every time I have tried MacPorts in order to get a redistributable product I have to bring most of the entire MacPorts system into the .app bundle including libc++ and libc which seems awfully fishy to me. Those are standard libraries that are on every OS X machine that is out there. > > However, that nor your kludge would have allowed you to find the glitch in > Digia's package - in the QtCore library I have installed through that same > installer (dated Jan. 5th of this year) that same library is referenced ... > > The proper way to repair this is > > %> install_name_tool -change /opt/local/lib/libz.1.dylib > /usr/lib/libz.1.dylib > /Users/Shared/Toolkits/Qt-5.4.0/5.4/clang_64/lib/QtCore.framework/QtCore > > That way you can use whatever bundling methods you use to bundle the Qt > libraries with your products. NO. The _proper_ way is that Digia's package is updated and corrected. Why do _I_ have to fix their problems. And why aren't they building on a completely clean OS X machine that just has the necessary Apple supplied compilers? > > R. > _______________________________________________ > Interest mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
