On Feb 6, 2015, at 3:48 PM, René J.V. Bertin <[email protected]> wrote:
> On Friday February 06 2015 13:12:32 Michael Jackson wrote: > >> 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. > > Evidently MacPorts isn't the most suitable choice in that case, and that's > why I queried about the kind of development you're doing. > >> 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. > > That's weird and shouldn't be necessary, but also a different topic. > >> >> 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? > > OK: >>> That way you can use whatever bundling methods you use to bundle the Qt >>> libraries with your products > < < until Digia fixes their installer > > I take it you have filed a bug report about this? ;) > > R. > Have not had a chance to file the bug yet. I guess it is one of those things that I am confused why no one else has seen the issue except me. Which is why I came to the list to make sure I had deduced the proper thing. Cheers for the weekend.. Mike J. _______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
