Hi Carsten,

again on this topic, I decided to not give up on this. I am wondering how
you actually build osgswig from the current source available. I have
examined the CMakeLists.txt files in the project and all I can say this is
available for python, perl and java only, from my little understanding of
CMake configuration.

In the main CMakeLists.txt line 174 is adding the src folder for the core
And this is the src CMakeLists

IF   (BUILD_OSGPYTHON)
    ADD_SUBDIRECTORY(python)
ENDIF(BUILD_OSGPYTHON)
IF   (BUILD_OSGPERL)
    ADD_SUBDIRECTORY(perl)
ENDIF(BUILD_OSGPERL)
IF   (BUILD_OSGJAVA)
    ADD_SUBDIRECTORY(java)
ENDIF(BUILD_OSGJAVA)

since I dont build it for any of these I am not surprised I am ending up
with empty project

Can you share the build setting for CMake? Thanks again

Nick


On Wed, May 21, 2014 at 3:54 PM, Trajce Nikolov NICK <
trajce.nikolov.n...@gmail.com> wrote:

> Thanks Robert, I will give it a try. Actually all I care for now is to see
> the Viewer into .NET control, do not care to much of the underlying
> approach - but simplier, better.
>
> > I had thought C# was going out of fashion with the advent of tablet
> and phones taking midshare and developer time...
>
> Nah, at least not in Macedonia. Here you can not find C++ job, all is
> .NET, C#, Java .. suddenly
>
> Thanks again,
> Nick
>
>
> On Wed, May 21, 2014 at 3:49 PM, Robert Osfield 
> <robert.osfi...@gmail.com>wrote:
>
>> Hi Nick et. al,
>>
>> I had thought C# was going out of fashion with the advent of tablet
>> and phones taking midshare and developer time...
>>
>> If you really need C# integration then perhaps just integrating the
>> top level classes like Viewer would be sufficient.
>>
>> Another possible route you could consider is writing C# integration
>> via the new osgDB::PropertyInterface class that I have written to
>> assist with scripting integration.  This class provides mechanisms for
>> interface discovery, property get/setting and method invocation, and
>> uses the new serializers under the hood. It's much lighter weight than
>> osgIntrospection as has a pretty mature scripting implementation in
>> the form of the new lua plugin.  The lua plugin could form as descent
>> example of how to use the new PropertyInterface class.
>>
>> Robert.
>> _______________________________________________
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
>
>
>
> --
> trajce nikolov nick
>



-- 
trajce nikolov nick
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to