[RFC] C-source code writing functionality for ApiTrace (glx/egl)
Juha-Pekka Heikkila
juhapekka.heikkila at gmail.com
Mon Apr 25 08:09:34 UTC 2016
Hi,
I'm replying to this old thread advertising I today pushed new version
of my c-source code writer to my old branch. Advertising mostly because
I noticed there are some people who maybe try to use this for something.
I've been writing it just for myself and code look like that -- 'works
for me' without cleaning any codes. I've concentrated almost only on glx
on Linux with some love for egl.
As a small 'how to' source codes written almost never are going to be
working straight out. Normally after trace has been written one need to
go look at data.c, includes.h and testmain.c
You'll need to go grep for 'glx_visual_params' and edit into testmain.c
the correct one, same goes for 'screensize' and possibly
'ContextAttribsARB'. One thing in testmain.c to pay attention is the
selection of GLXFBConfig, currently selection is made with values on
GLX_SAMPLE_BUFFERS. If one compile debug build information about this
will be printed on stdout at runtime.
Anyhow, the branch is here:
https://github.com/juhapekka/apitrace-1/tree/c_source_code_writer
/Juha-Pekka
More information about the apitrace
mailing list