Mac-related changes in 1.9

[corristo]

Hi,

Tried to build Ogre 1.9 recently. Noticed that all components and plugins became a frameworks instead plain dylibs.

Is there any particular reason for that? I'm asking because it brakes my build & autopackaging workflow for OpenMW entirely
Is installing Ogre using "make install" unsupported now?

[corristo]

Also static build fails because of mesh upgrader & xml converter linking errors

Code: Select all

Linking CXX executable ../../bin/OgreXMLConverter
Undefined symbols for architecture x86_64:
  "_CFBundleCopyBundleURL", referenced from:
      Ogre::macFrameworksPath() in libOgreMainStatic.a(macUtils.mm.o)
      Ogre::macPluginPath() in libOgreMainStatic.a(macUtils.mm.o)
      Ogre::macBundlePath() in libOgreMainStatic.a(macUtils.mm.o)
  "_CFBundleCopyResourceURL", referenced from:
...

[masterfalcon]

The reason for switching to frameworks instead of dylibs is that it makes it much less complex to put together an app(they all go in Frameworks now) and they can be more logical development resources.

I have a fix for the tools that I'll push tonight.

Installing with make install should still work, file a bug if it is not working.

[corristo]

I reported one issue: https://ogre3d.atlassian.net/browse/OGRE-265