Hello all,
I have a few questions about the MacOS X build. I believe now the build
all happens through CMake right? Can I build binaries of OSG that would
support both 32 and 64 bit intel?
I guess for this to work, I need all third-party libraries OSG links
with to be also 32+64 bit? Is ther
Hi,
Am 08.12.10 16:14, schrieb Jean-Sébastien Guay:
> I have a few questions about the MacOS X build. I believe now the build
> all happens through CMake right? Can I build binaries of OSG that would
> support both 32 and 64 bit intel?
yes. Afaik you'll have to target 10.6 as older systems only s
Jean,
I build universal binaries on OSX just fine. I run Snow Leopard (10.6.x), but
I generate code compatible with 10.5. I build all of my 3rd party libraries
manually, which is sometimes a pain as some packages are not friendly to
universal builds. In those cases, the configure script bomb
Hi Jean-Sébastien,
you can build universal binaries with intel 32 and 64 bit support, just
change CMAKE_OSX_ARCHITECTURES to "i386;x86_64".
Of course you have to make sure that all your third-party libraries are
"universal" and contain the architectures you intend to support.
ImageIO and Cocoa
Hi Chuck,
Am 08.12.10 16:43, schrieb Chuck Seberino:
> Same thing with imageIO. That means you need to build your own png, gif,
> jpeg and tiff libraries since it won't use QuickTime (32-bit only). Once
> your dependencies are ready, it is pretty straightforward to build OSX.
ImageIO can han
Hi Stephan,
Somehow I knew you would answer :-)
freetype is part of the system and should be 32+64bit.
I'd stick with one backend, namely Cocoa, as it supports 32bit and 64bit
out of the box. The carbon backend is deprecated.
ImageIO supports 32 and 64bit.
OK, seems I'm set. For OSG at least.
Hi Chuck,
I typically build with Makefile support, but the XCode generator works as well.
Interesting, so I could make CMake generate makefiles, build OSG that
way, and then inspect the makefiles to find out how to do the same thing
for our own SDK.
Thanks a lot for your help,
J-S
--
Hi again,
I just wanted to chime back, now that the OSG build is done. I am
surprised / delighted at how painless it was.
I configured for a makefile build, set the following as advised:
CMAKE_OSX_ARCHITECTURES = i386;x86_64
OSG_DEFAULT_IMAGE_PLUGIN_FOR_OSX = imageio
OSG_WINDOWING_SYSTEM = Co
On 08-12-2010, at 19:13, Jean-Sébastien Guay wrote:
> BTW, I found that using macports you can add "+universal" to the command to
> make it build universal binaries, as defined by the universal_archs directive
> in macports.conf (set to "x86_64 i386" by default, so that's what I want). So
> th
Hi Erik,
Perhaps a nice tip: I found it convenient to enable building the universal
variant automatically on all ports that are installed by adding the +universal
line in /opt/local/etc/macports/variants.conf
Indeed, good tip, I was just adding +universal to all my port ...
commands manuall
HI J-S,
Can't comment much about the fink-stuff...
Am 08.12.10 17:08, schrieb Jean-Sébastien Guay:
> How do you tell CMake to build frameworks? Or does it do it by default?
> Also how do you tell CMake to build universal binaries?
Just set OSG_COMPILE_FRAMEWORKS to TRUE and
OSG_COMPILE_FRAMEWOR
Hi Stephan,
Just set OSG_COMPILE_FRAMEWORKS to TRUE and
OSG_COMPILE_FRAMEWORKS_INSTALL_NAME_DIR accordingly. (If you want to
embed the frameworks within your application-bundle, use
"@executable_path/../Frameworks", otherwise something like
"/Library/Frameworks"
Thanks, good to know.
J-S
--
_
12 matches
Mail list logo
