[epiar-devel] Merging Branches
chris at epiar.net
Sun Dec 6 00:47:16 PST 2009
Good work so far! We need to start merging branches though before we keep going. I imagine we'll have to do this every couple of weeks.
Non-optional recommendations (though open for discussion):
* Quadtree branch is good.
* PhysicsFS branch runs, very slowly. We need to 1) resolve build issues, 2) do a heavy evaluation on the usefulness of physicfs. I've asked iccululs if physicfs' build system requires cmake. That would be bad. I also have no idea if it's dirty yet. I haven't looked because 3) it runs too goddamn slow, almost surely do to the profiler code, which is nicely resolved by 4) we should not have profiler code in Epiar. See gprof, etc. gprof can do a more accurate timing job anyway, and it's an industry skill to know a profiler, no offense. I appreciate the work though and I hope I don't sound too rude, but unless you want to argue the point, that code needs to be removed before we merge.
* GL optimization branch. I didn't look at this much. What was done exactly?
Anybody else need to ask questions before we go on holiday break and might not hear actively back from each other until two weeks before the deadline?
Chris Thielen <chris at epiar.net>
More information about the epiar-devel