[KDE/Mac] More audio strangeness

Jeremy Whiting jpwhiting at kde.org
Sat Jan 17 11:24:01 UTC 2015

I use -developer-build so I don't have to do a make install, just make and
point my variables (PATH, QT_PLUGINS etc.) into my build folder. I use this
when I build my own qt on linux and it works well, but maybe it's not
needed and I ought to be doing make install into some prefix anyway like
you are. I don't really need/want a release build just yet, but I will once
stuff starts to work if I start putting together installers and such, so I
am curious how that works, thanks for asking on the interest list.

On Sat, Jan 17, 2015 at 2:26 AM, René J.V. <rjvbertin at gmail.com> wrote:

> On Friday January 16 2015 21:22:34 Jeremy Whiting wrote:
> >My configure line is this:
> >../qt5/configure -debug -separate-debug-info -system-zlib -system-libpng
> >-system-libjpeg -system-sqlite -dbus-linked -nomake examples -nomake tests
> >-confirm-license -opensource -developer-build -no-frameork
> >-I/opt/local/include/dbus-1.0 -L/opt/local/lib I've also set CFLAGS to
> >-isystem/opt/local/include and CXXFLAGS the same.
> Mine is configure -prefix /opt/local -archdatadir /opt/local/libexec/qt5
> -docdir /opt/local/share/doc/qt5 -headerdir /opt/local/include/qt5
> -plugindir /opt/local/share/qt5/plugins -importdir
> /opt/local/share/qt5/imports -qmldir /opt/local/share/qt5/qml -datadir
> /opt/local/share/qt5 -libdir /opt/local/libexec/qt5/Library/Frameworks
> -bindir /opt/local/libexec/qt5/bin -libexecdir
> /opt/local/libexec/qt5/libexec -translationdir
> /opt/local/share/qt5/translations -sysconfdir /opt/local/etc/qt5
> -examplesdir /opt/local/share/qt5/examples -testsdir
> /opt/local/share/qt5/tests -hostbindir /opt/local/libexec/qt5/bin
> -hostlibdir /opt/local/libexec/qt5/Library/Frameworks -hostdatadir
> /opt/local/share/qt5 \
>         -v -release -opensource -confirm-license -shared -force-pkg-config
> -no-mtdev -no-harfbuzz -openssl-linked -no-xinput2 -no-xcb-xlib -no-libudev
> -no-egl -make libs -make tools -nomake examples -nomake tests -verbose -nis
> -cups -iconv -no-evdev -icu -fontconfig -no-pch -dbus-linked -no-xcb -glib
> -directfb -no-linuxfb -no-kms -framework -optimized-qmake -no-sql-db2
> -no-sql-ibase -no-sql-mysql -no-sql-oci -no-sql-odbc -no-sql-psql
> -no-sql-sqlite -no-sql-sqlite2 -no-sql-tds -platform macx-clang -no-openvg
> -force-debug-info -no-strip -no-separate-debug-info
> So a release build with obligatory, embedded debugging information that
> won't be stripped.
> >So are you saying that
> >-debug and -separate-debug-info are conflicting arguments? i.e.
> >-separate-debug-info should only be used when doing a release build?
> I can't answer that. I'm not sure what each of those does on OS X, but
> yes, it does seem that -debug and -separate-debug-info might conflict. And
> then there's the -developer-build option you use. That's really for people
> working *on* Qt as far as I understand, which I think is not really your
> case, is it?
> What exactly are the reasons you want debug information in Qt itself? In
> my case I just want to be able to have line numbers on the Qt code in crash
> backtraces. If that leads me to believe I have a real bug in Qt, I simply
> rebuild the file in question with full debug (and -O0). One apparently
> needs to keep the .o files around anyway on OS X *) so that's just kind of
> an incremental rebuild that doesn't take much time.
> *) maybe that's the result of -no-separate-debug-info??
> BR
> RB :)
> _______________________________________________
> kde-mac at kde.org
> List Information: https://mail.kde.org/mailman/listinfo/kde-mac
> KDE/Mac Information: http://community.kde.org/Mac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20150117/9b108152/attachment.html>

More information about the kde-mac mailing list