On 14-Jan-09, at 1:01 PM, Nick Guenther wrote: > Why do we need to compile Qt on OS X with --no-framework? Do you have > to do this on Linux and Windows? Getting Qt compiled is the signal > largest stumbling block to getting a Mixxx development environment set > up. If I could hack this out I'd do it so fast.
I started doing this because I found packaging was less of a pain in the ass if I was bundling the .dylibs instead of the entire framework folders on OS X. You can compile without this flag, but you may need to edit the SConscript to make it use the Qt in framework form (as opposed to just straight .dylibs). If I remember right, I did originally have the SConscript using Qt as a framework and that code might still be in the SConscript, just commented out. If you want to build packages though, you'll definitely have to edit that create_osx_dmg.sh script that I wrote, and you may run into the same problem I had before that made me switch to --no-framework. (I totally forget what the problem was though...) Thanks, Albert ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
