Re: Building ORBit2 on Windows

["Frank.Rehberger" <Frank Rehberger web de>]

DII  stands for Dynamic Invocation Interface.

Either one is using the static marshalling/demarshalling code being
generated from IDL files or one can use the DII interface to assemble
the requests and de-assemble the replies for arbitrary object interfaces
and functions. But DII was used mostly to realize non-blocking remote
invocations as DII also provides a polling mechanism for replies of
concurrent  requests.

To meet the need for non-blocking concurrent remote invocations, OMG
defined the Messaging Interfaces in later CORBA releases, based on
callback interfaces and easier to use. So the interest for DII vanished.

ORBit2 did not implement DII interfaces, nor does it implement the
Messaging features. 

DII is cumbersome to use. Instead ORBit2 provides a generic
serializer/deserializer traversing the corresponding type-structure
(tree) for each function parameter. These type-structures are embedded
into the sources generated by IDL compiler.

This allows something like DII. PyOrbit2 once allowed to read arbitrary
IDL files and generate dynamicly the corresponding type-structures and
use them for any dynamic remote invocations with Python. PyORBit2 is
outdated, not maintained anymore, but the sources should be in
repository here:

http://freshmeat.net/projects/pyorbit

Hope that helps,
Frank


Tor Lillqvist wrote:
>> Well, I'm thinking of something like the files here:
>> http://ftp.gnome.org/pub/GNOME/binaries/win32/ORBit2
>>
>> (which I've never tried to use), since my purpose is to implement DII,
>> so I need to modify the ORBit2 library itself.
>>     
>
> I still don't understand what you mean with "implement Dll"...
>
> You can have a DLL (or several) with your own code that calls
> functions from the ORBit2 DLL(s).
>
> Do you just want to minimize the number of DLLs needed? But then you
> would need to compile libIDL and GLib yourself, too, as static
> libraries to link into your DLL.
>
>   
>> I'm using an SMB mount onto my Linux file system, so they actually are
>> symlinks.
>>     
>
> Ah ok.
>
>   
>> Here's more of what I've found out.  I installed the Windows debugging
>> tools
>>     
>
> Those unfortunately don't help much for code built with MinGW, as it
> uses a different debugger symbol table format.
>
>   
>> Now, I'm not quite sure how to read this.  Was it trying to load
>> libgthread when it died,
>>     
>
> I think so, or then libgthread is just the last DLL it loaded before
> the crash then happens while it was doing something else... Sorry, I
> can't see any obvious cause for the crash in that output either.
>
>   
>> checking for msgfmt... no
>>     
>
>   
>> Yes, I've installed gettext-runtime-0.17-1.zip and
>> gettext-runtime-dev-0.17-1.zip
>>     
>
> You need the msgfmt command when building GLib, that is in the
> "gettext-tools" package on ftp.gnome.org.
>
> --tml
> _______________________________________________
> orbit-list mailing list
> orbit-list gnome org
> http://mail.gnome.org/mailman/listinfo/orbit-list