Building on Mac OS X

[Stephen Kelly]

I discussed a bit off-list with José, and discovered that a colleague could
successfully run apitrace on a mac, and discovered I could create a new
user account on mine which could run it.

I then realized that the problem was I had DYLD_IMAGE_SUFFIX=_debug in my
environment. Removing that fixed the problem. Maybe apitrace could check
that and issue an informative error message.

Also, the Qt5 branch in the repo should maybe be rebased :).

Thanks,

Steve.



On Tue, Dec 2, 2014 at 11:58 AM, José Fonseca <jose.r.fonseca at gmail.com>
wrote:

>
>
> On Tue, Dec 2, 2014 at 9:49 AM, Stephen Kelly <steveire at gmail.com> wrote:
>
>> Zack Rusin <zack <at> kde.org> writes:
>>
>> >
>> > On Mon, Dec 1, 2014 at 2:20 PM, José Fonseca <jose.r.fonseca <at>
>> gmail.com> wrote:I never tried building with the "Xcode" generator. I
>> always use the default "Unix Makefiles" generator.
>> > Does the issue happen with the Unix Makefiles cmake generator too?
>> >
>> >
>> > Nah, those work correctly. Xcode generator has been broken for a while
>> (maybe even always). I use 'ninja' because it's faster than the
>> alternatives but both unix makefiles and ninja work fine.
>>
>> Ok, I tried the makefiles generator again and I got it to build. I think
>> the problem I hit before was a bad clang installation.
>>
>> However, it doesn't work for me:
>>
>>  ~/dev/src/apitrace/build (master) $ ./apitrace trace
>> ~/dev/prefix/bin/qmlscene
>>  apitrace: loaded into /Users/ske/dev/prefix/bin/qmlscene
>>  apitrace: tracing to /Users/ske/dev/src/apitrace/build/qmlscene.trace
>>
>>  ~/dev/src/apitrace/build (master) $ DYLD_FRAMEWORK_PATH=$PWD/wrappers
>> ~/dev/prefix/bin/qmlscene
>>  apitrace: loaded into /Users/ske/dev/prefix/bin/qmlscene
>>  apitrace: tracing to /Users/ske/dev/src/apitrace/build/qmlscene.1.trace
>>  Segmentation fault: 11
>>  ~/dev/src/apitrace/build (master) $ l $PWD/wrappers/
>>  CMakeFiles          Makefile            OpenGL.framework    cgltrace.cpp
>>        cmake_install.cmake
>>  ~/dev/src/apitrace/build (master) $
>>
>> Any guidance from here?
>>
>
> Pull the latest changes (in order to pick up
> https://github.com/apitrace/apitrace/commit/8695c248b5347120bf56c3d1a3a8493d791ea712
> ) and do
>
>    ./apitrace trace --verbose --debug ~/dev/prefix/bin/qmlscene
>
> to run inside LLDB and provide the stack back trace.
>
>
>
>> For example, is there a requirement that apitrace and Qt (and anything
>> else - what else?) is compiled with the same compiler?
>>
>
> No.
>
>
>> In this case, Qt and apitrace are compiled with the same compiler, (a
>> self-built clang), but if there are other dependencies coming from the
>> system, then they were not compiled with the same compiler.
>>
>> Is there a simpler testcase available than Qt?
>>
>>
>>
> Yeah, there's a test suite composed of simple test cases on
> https://github.com/apitrace/apitrace-tests and I run it continuously on
> MacOSX.
>
> Jose
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/apitrace/attachments/20141204/d7f16a58/attachment.html>