PocketMatrix

Statically link ?

I think that evc does not include not used functions.

well, the problem is that for a general implementation of a 3D API like OpenGL (and not a specific game) you don't know in advance which functions are going to be needed by a programmer.

you are right that obviously a small number of functions will be used more often than most others. that's why i allow developers to choose in the python script which functions will be created. at the moment i don't have a fall-back for those functions that were not selected (so the library complains about this instead of doing it at least slowly) but that's going to come.

but i'd love to see a better solution to this...

thx,
DANIEL

hey thanks, this looks VERY interesting.

i have to admit that i first want to try out the Mesa way: filling a pixel-buffer for each "feature" (such as texture, shading, etc...) and finally combine them in the way as required.

i used to think that this would be very slow, but the buffers should fit nicely into the cache and other than i used to believe, an early z-test can be done efficiently (due to the fact that pixels will not switch frequently between visible and unvisible).

if it should turn out, that this solution is ways slower than what i have right now i'll definitely try out the assembler stuff. what's keeping me away from it right now is the fact that i'll have to learn ARM assembler...

thanks,
DANIEL

I'd use CacheSync, but you might want to look at .