Re: [Interest] My first OSX compile ends in error.

2015-06-30 Thread Thiago Macieira
On Tuesday 30 June 2015 23:29:47 Jason H wrote: > Hrm... So after playing some more, removing the entry in main.cpp, it works. > I need a better way to appropriately include Q_IMPORT_PLUGIN(QSvgPlugin) I > thought it was needed on all __APPLE__ platforms, but it seemingly isn't It's needed on #ifd

Re: [Interest] My first OSX compile ends in error.

2015-06-30 Thread Hamish Moffatt
On 01/07/15 07:29, Jason H wrote: > Hrm... So after playing some more, removing the entry in main.cpp, it works. > I need a better way to appropriately include Q_IMPORT_PLUGIN(QSvgPlugin) > I thought it was needed on all __APPLE__ platforms, but it seemingly isn't > Only needed if you are staticall

Re: [Interest] My first OSX compile ends in error.

2015-06-30 Thread Jason H
t;Jason H" > To: "interest@qt-project.org" > Subject: [Interest] My first OSX compile ends in error. > > Normally I build on Linux, or when building on OSX, for iOS. But this is my > first stab at running the QML app on OSX. > > Undefined symbols for architecture x86

[Interest] My first OSX compile ends in error.

2015-06-30 Thread Jason H
Normally I build on Linux, or when building on OSX, for iOS. But this is my first stab at running the QML app on OSX. Undefined symbols for architecture x86_64: "qt_static_plugin_QSvgPlugin()", referenced from: main::StaticQSvgPluginPluginInstance::StaticQSvgPluginPluginInstance() in mai