i’ve been working on this and am confused thusly:
in python, loading libpandagl fails, complaining about libmkl_def.dylib:
>>> selection = GraphicsPipeSelection.getGlobalPtr()
>>> selection.printPipeTypes()
:display: loading display module: libpandagl.dylib
:display: Unable to load: dlopen(libmkl_def.dylib, 1): image not found
Known pipe types:
(all display modules loaded.)
>>>
in c this code
void * x = dlopen("/usr/local/panda/lib/libpandagl.dylib",1);
printf("%i\n",x);
if (x == (void *)NULL){
printf("fail\n");
printf("%s\n",dlerror());
}
else printf("pass\n");
loading fails with a different message:
% ./libtest
0
fail
dlopen(/usr/local/panda/lib/libpandagl.dylib, 1): Symbol not found: _PyObject_Free
Referenced from: /usr/local/panda/lib/libinterrogatedb.dylib
Expected in: dynamic lookup
for completeness, opengl loads fine (no surprise, since other opengl programs have been running):
void * = dlopen("/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib",1);
printf("%i\n",x);
if (x == (void *)NULL){
printf("fail\n");
printf("%s\n",dlerror());
}
else printf("pass\n");
yeilds
% ./libtest
1049136
pass
so libpandagl fails in two different ways. the problem in the c instance seems to be some sort of library path problem, but i haven’t explored that fully.
let me also mention that i’ve successfully built and run a 1.4.x panda from CVS in the past. i can’t be certain of the exact version – it was about 15 months ago. the main differences between that (working) time and this are: building with support for opencv and nvidia cg. i also upgraded the cg framework on this machine, but since it wasn’t incorporated in the last build, i wouldn’t imagine that has much to do with it.
jeremy