openni and primesense/kinect status

[Hans-Christoph Steiner]

On May 30, 2011, at 12:45 PM, Jonas Smedegaard wrote:

> On 11-05-30 at 12:22pm, Hans-Christoph Steiner wrote:
>
>> third attempt failed at missing libopenni-dev
>> ---------------------------------------------
>> g++ -g -O2 -malign-double -O3 -fno-tree-pre -fno-strict-aliasing
>> -DNDEBUG -msse3 -mssse3 -I../Players -I/usr/include/nite
>> -I/usr/include/ni -DUSE_GLUT -DXN_SSE -M -MF Release/main.d -MT
>> "./Release/main.o Release/main.d" ../Players/main.cpp
>> ../Players/main.cpp:8:22: fatal error: XnOpenNI.h: No such file or
>> directory
>
> Beware of the optimizations: Debian Policy mandates ability to disable
> optimizations, so if above -O3 is applied by upstream (or hardcoded in
> your build rules) then it is most likely done wrong.
>
> I cloned the project to try have a closer look, but apparently picked
> the wrong one (openni) - no O3 mentioned anywhere in source code.  But
> doing so I noticed several tarballs inside the git - that looks bad!


Yeah, the upstream source is a mess for all this, there are mostly no  
official release tarballs, except for the binary one.  The free  
software library and modules are only in git, but they don't develop  
out of that git.  They post different versions into different  
branches, like the 'stable' version is only in the master branch, and  
the 'unstable' version is in an 'unstable' branch, but that 'unstable'  
branch does not included the 'stable' release.

So, on that note, the optimization flags are in the upstream build  
system.

.hc


----------------------------------------------------------------------------

Using ReBirth is like trying to play an 808 with a long stick.    - 
David Zicarelli