Patrick Hartling wrote:
> On Nov 6, 2008, at 7:06 AM, Marcus Lindblom wrote:
> 
>> Hi,
>>
>> I noticed there is a branch for trunk migration in the pyopensg repo,
>> but no commits have been done yet? Are there local changes 'in the
>> works' somewhere, or can I start planning to push patches there?
>> (Using hgsubversion or git-svn or something similar)
> 
> I started working on the transition to the trunk a few months ago, but I 
> ran out of time. The code that I committed to that branch is the 
> in-progress work. I don't think that it all compiles, and thus I did not 
> get to a point where I could validate that the new field container 
> pointer handling is correct.

Ok? But.. the trac browser shows absolutely no commits other than a copy 
to create the branch from trunk?

https://realityforge.vrsource.org/trac/pyopensg/changeset/540/branches/trunk_update

>> Also, I've tried to build things on windows, and it doens't go
>> completely haywire.. yet. :) So there's hope.
>>
>> However, there are some immediate with compiling
>> osgmodule_mainheader.cpp, which I think might be more related to
>> opensg-trunk changes rather than pyopensg.
>>
>> * OSGFieldContainerPtr.h does not exist (trunk-compability issue?). I
>> removed that include and edited some files to make it work.
> 
> Bear in mind that the PyOpenSG C++ code is generated by Py++. It is not 
> meant to be edited by hand.

Yup, but it seemed as if the osgmodule_... file was handcrafted, and 
I've mainly worked with that as a start.

>> * OpenSG/OSGPerfMonitor.h not found (I've compiled OpenSG2 with
>> NVPerfSDK, but no such files appear in the include-dir?) What do I need
>> to do to make that happen?
> 
> There are many changes left to merge from the fcptr_stable_jun07 OpenSG 
> branch to the trunk. The performance monitoring is included with that.

Ah.

> I started working on that, too, but I left out the controversial stuff and 
> things that were unfamiliar to me because I did not want to raise 
> anyone's hackles. Allen had said he would take care of the merging back 
> when the fcptr_stable_jun07 branch was created, but these days, I doubt 
> he has any time to spare for this work.

Hm. Ok. But I have some time for this. So, my options are to merge the 
perfmon stuff to trunk in the opensg-repo, or to remove it from my 
pyopensg copy?

Cheers,
/Marcus

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to