Re: Macports and Qt development
Am 05.03.2012 um 01:10 schrieb James Linder: Your mail implies you'd install Qt via macports. Why would one do that instead of installing the Qt SDK ? All the command line tools are available in the SDK (in fact I do not even know if qtbuilder works, I'm sure it does though.) well, I would like to use MacPorts for controlling what I have on my computer. Specially the developer tools. Specially because I can activate/deactivate libraries and install different versions of them quite fast. If you were installing a package that needed Qt would not macports install Qt as needed and transparently? normally yes. Packages that depend on Qt install Qt transparently, but not in a developer friendly way Again, pardon my ignorance, debug with a framework ??? ummm qDebug() and gdb ??? I meant I would like to debug my program without problems and thousand of warning messages. As a developer I want to use gdb for debugging... and sometimes that can only be done if Qt was installed with the +framework. However doing so will make Qt dependent packages break. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Macports and Qt development
Hi! I would like to know if other Mac/Qt (optionally also Python) developers are having as many problems as I do. MacPorts installs Qt as a normal library, although there is a variant (non default) that will compile it as a OSX framework. That is fine for non developers, but I noticed that not having a framework is a nightmare if I want to debug my Qt apps. Some times I am forced to compile without debug info, other times my screen get full of warnings about missing symbols. In those cases I can debug my code if I filter out all the warnings I get with every debugger step. For some reason, lately I can no longer debug without thousand of warnings a hello world in qt. Something which could be fixed before with DYLD_IMAGE_SUFFIX=_debug Also I use a lot pyside and ipython, which do not compile if Qt was installed as a framework. Therefore it is hard to debug apps with them My solution so far is installing the official Qt binaries which are compiled as a framework. Since that is the official default, I suppose that is the reason I no longer have problems working with other Qt related tools such as Pyside and iPython gui. So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? cheers, Francisco ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports and Qt development
On 4 mar 2012, at 14:46, Francisco García wrote: So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? This is my own opinion. If you're a developer relying on a framework, you depend on that framework in a wholly different way than a user of an application that has been developed against that framework, exactly as you describe with your debugging woes. If you've had success with the official distribution I'd say go with that. If it's compiled as a framework there isn't any reason it can't integrate with most things built in Macports, with just a little, or even no configuration. It's still useful to know your experience as a developer in using Qt installed from Macports as it can inform others. It would also be useful to know what version of OS X you are on, and which version of Xcode you use, if you do. By using the official Qt distribution you can also follow official documentation and know that it's valid for your situation. A quick search tells me that even with an installation of the official Qt distribution, debugging isn't always painless to get working: http://qt-project.org/wiki/Mac_OS_X_Troubleshooting http://qt-project.org/doc/qt-4.7/debug.html#id-648ce576-8473-4375-80b9-0dad5c38b6ef hope that helps, -- Daniel ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports and Qt development
On 04/03/2012, at 11:00 PM, macports-users-requ...@lists.macosforge.org wrote: Hi! I would like to know if other Mac/Qt (optionally also Python) developers are having as many problems as I do. MacPorts installs Qt as a normal library, although there is a variant (non default) that will compile it as a OSX framework. That is fine for non developers, but I noticed that not having a framework is a nightmare if I want to debug my Qt apps. Some times I am forced to compile without debug info, other times my screen get full of warnings about missing symbols. In those cases I can debug my code if I filter out all the warnings I get with every debugger step. For some reason, lately I can no longer debug without thousand of warnings a hello world in qt. Something which could be fixed before with DYLD_IMAGE_SUFFIX=_debug Also I use a lot pyside and ipython, which do not compile if Qt was installed as a framework. Therefore it is hard to debug apps with them My solution so far is installing the official Qt binaries which are compiled as a framework. Since that is the official default, I suppose that is the reason I no longer have problems working with other Qt related tools such as Pyside and iPython gui. So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? Your mail implies you'd install Qt via macports. Why would one do that instead of installing the Qt SDK ? All the command line tools are available in the SDK (in fact I do not even know if qtbuilder works, I'm sure it does though.) If you were installing a package that needed Qt would not macports install Qt as needed and transparently? Again, pardon my ignorance, debug with a framework ??? ummm qDebug() and gdb ??? Thanks James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Macports and Qt development
On Mar 4, 2012, at 09:16, Daniel Ericsson wrote: On 4 mar 2012, at 14:46, Francisco García wrote: So the big question for MacPort users is: Do Qt developers manage their packages with MacPorts or just run away from it when there is something that involves Qt? This is my own opinion. If you're a developer relying on a framework, you depend on that framework in a wholly different way than a user of an application that has been developed against that framework, exactly as you describe with your debugging woes. If you've had success with the official distribution I'd say go with that. If it's compiled as a framework there isn't any reason it can't integrate with most things built in Macports, with just a little, or even no configuration. It's still useful to know your experience as a developer in using Qt installed from Macports as it can inform others. It would also be useful to know what version of OS X you are on, and which version of Xcode you use, if you do. By using the official Qt distribution you can also follow official documentation and know that it's valid for your situation. A quick search tells me that even with an installation of the official Qt distribution, debugging isn't always painless to get working: http://qt-project.org/wiki/Mac_OS_X_Troubleshooting http://qt-project.org/doc/qt-4.7/debug.html#id-648ce576-8473-4375-80b9-0dad5c38b6ef However, be aware that having the official Qt SDK installed (which will install frameworks in /Library/Frameworks, right?) might cause problems if you then try to install MacPorts ports that use Qt (as would be the case for any other port you install that uses libraries for which you've also installed frameworks in /Library/Frameworks or libraries in /usr/local). ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
