Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
SVN Update - Note things are broken, use Rev #184
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post will appear after it is approved by moderators
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Andy Miller  
View profile  
 More options Feb 15 2007, 8:27 pm
From: "Andy Miller" <nzmill...@gmail.com>
Date: Fri, 16 Feb 2007 09:27:45 +0800
Local: Thurs, Feb 15 2007 8:27 pm
Subject: SVN Update - Note things are broken, use Rev #184

Team

I'm in the middle of a series of code generator updates, with the intention
that it becomes even more (Ogre) version independant and is simpler to
maintain...

However I'm also sending through Py++ updates to Roman as I go and hence
there is a small disconnect between the SVN;s at the moment..

You "should" use Python-Ogre SVN Rev #184 until further notice..

However, if there are any Unix people that want to test the new updates then
you can copy the attached file into your
PYPLUS\pyplusplus_dev\pyplusplus\function_transformers directory, "python
setup install" Py++, get the "release" version of Ogre (no patching!), run
generate_code and see if it compiles..

Changes I've made are:
     1. Automatically exclude "static const" vars that have their value set
in the header file.
     2. Change functions that take void * in their argument list to instead
take an unsigned int

With #1 the vars are no longer exported - however I'm still exposing
functions that use these vars in their argument lists, so I want to
understand if things compile or if I need to handle the function definations
as well - I've only done this with Ogre, if it works I'll do the same with
OIS etc

#2 is so we can use CTypes to create and manage "raw" buffers, and then pass
the address of these buffers to Ogre..

On the to do list (which will also need Py++ changes) is to have functions
that return pointers (void *, uchar*, float * etc) also return unsigned ints
so we can again use CTypes to manage the raw buffers..

Cheers

Andy

  transformers.py
28K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »