Re: [Opensg-core] OpenSG 2 python bindings

[Patrick Hartling]

On Jan 11, 2011, at 7:34 AM, Patrick Hartling wrote: On Jan 11, 2011, at 1:49 AM, Gerrit Voß wrote: Hi, as this came up internally, can somebody give me a hint as to the status and where I can get started to look at it. It seems more sooner than later that I will need some form of (at least basic) script support. So I would like to have another structured go at it ;) PyOpenSG is up to date with r2500 of the SVN trunk and is working well on Linux and Windows. I've only tested 32-bit builds on Windows, but I would like to try a 64-bit build soon. The project is hosted here: http://code.google.com/p/pyopensg/ I did have to make some patches to OpenSG get PyOpenSG to compile and link, and I have yet to submit them to this forum for review. I'll take care of that today. I haven't tried to update to r2512, but it probably should go smoothly. As promised, here are the patches: add-FogChunk-methods.patch: Adds missing method definitions to OSG::FogChunk to fix linker errors. add-TreeBuilderBase-getNodePool.patch: Adds a missing method definition to OSG::TreeBuilderBase to fix a linker error. fix-64bit.patch: Fixes a compiler error when targeting 64-bit architectures. I am not sure why this one bit only us. In retrospect, this change may have been to silence a compiler warning rather than to fix an error. fix-Image-clearData.patch: Fixes the implementation of OSG::Image::clearData() to behave the way it was intended. fix-build-errors.patch: For various instantiations of OSG::Point<V,S> and OSG::Vector<V,S>, compiler errors occurred without these changes. The second block is the critical part. As I recall, Visual C++ reported overload ambiguity errors because it could not deduce the type of multiplying a float by the result of OSG::Vector<V,S>::dot() for some V (OSG::Uint8 maybe?). I have a standalone test program somewhere that demonstrates the issues if this one needs further clarification. fix-build.patch: Fixes the build to ensure that the correct FreeType ft2build.h is used. (We have our own FreeType build that we use for OpenSG and other packages, so it is important that the OpenSG build pick up the correct headers.) fix-gdal-include.patch: I haven't seen a GDAL installation where the GDAL headers are under a gdal subdirectory. The build should allow the path to the directories containing the GDAL headers to be specified, right? With those patches applied to r2500, the current PyOpenSG SVN trunk compiles and links.  -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ The information transmitted in this communication is intended only for the person or entity to which it is addressed and contains proprietary material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.

add-FogChunk-methods.patch
Description: Binary data

add-TreeBuilderBase-getNodePool.patch
Description: Binary data

fix-64bit.patch
Description: Binary data

fix-Image-clearData.patch
Description: Binary data

fix-build-errors.patch
Description: Binary data

fix-build.patch
Description: Binary data

fix-gdal-include.patch
Description: Binary data

------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to 
best implement a security strategy that keeps consumers' information secure 
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl 
_______________________________________________
Opensg-core mailing list
Opensg-core@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-core