apitrace on OS X

[Peter Lohrmann]

Now that I've got everything compiling correctly, I'm experiencing other issues that hopefully someone has encountered and knows a workaround for. I've been able to successfully use apitrace on a simple sample app (OSXGLEssentials), but am encountering other issues when trying trace a more complicated app.

if I use the recommended DYLD_LIBRARY_PATH approach, the app fails to load other libraries and doesn't run (I will investigate this issue, as its likely something simple). If I use DYLD_INSERT_LIBRARIES and DYLD_FORCE_FLAT_NAMESPACE=1, the application runs correctly and generates a trace file, but only CGL calls are recorded into the trace and none of the gl* calls. Any suggestions?

Thank you all,
Peter

From: José Fonseca [mailto:jose.r.fonseca at gmail.com]
Sent: Tuesday, May 14, 2013 11:13 PM
To: Peter Lohrmann
Cc: Apitrace list
Subject: Re: apitrace on OS X



On Wed, May 15, 2013 at 1:54 AM, Peter Lohrmann <peterl at valvesoftware.com<mailto:peterl at valvesoftware.com>> wrote:
Looks like the library I was generating was x86_64, but the application was strictly i386.  It took a bit of messing around with the project settings to get it to output just a 32-bit version, and then it seems the generated library went to a different directory /ApiTrace/build/wrappers/Debug instead of /ApiTrace/build/Debug/wrappers.
That's peculiar, as CMakeLists.txt should have built both architectures:

  # On Mac OS X build fat binaries with i386 and x86_64 architectures by default.
  if (APPLE AND NOT CMAKE_OSX_ARCHITECTURES)
      set (CMAKE_OSX_ARCHITECTURES "i386;x86_64" CACHE STRING "Build architectures for OSX" FORCE)
  endif ()

What XCode version did you use? Did you use cmake and make to build from commandline, or something different?

Jose
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20130525/ac0a988c/attachment.html>