[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Extending dcopidl2cpp
From:       Mathieu Chouinard <chouimat () videotron ! ca>
Date:       2001-12-17 17:20:52
[Download RAW message or body]

On December 17, 2001 12:14 pm, ian reinhart geiser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings
> 	I have been playing with sip for the last few weeks and decided that there
> are some real problems with building sip files.  I was looking at
> dcopidl2cpp and wondering how hard it would be to get it to build other
> bindings on the fly from the idl files.
>
> So far I have a dcopidl2sip binary, that will read the IDL file and
> generate the sip header.  Where I am stuck is how to get the build
> enviroment to call the correct tools from the following header:
>
> 	class foo : public bar()
> 	{
> 		SOME_MACRO	// <- would this tag trip dcopidl?
>
> 		sip_wrapper:	//  <-  is this correct too?
>
> 		void some_bar_member( int arg ) = 0;
> 		int some_other_bar_member( ) = 0;
> 	};
>
> What I would like it to do is process it with dcopidl and create an IDL
> file. And then process it with my dcopidl2sip converter.  From here valid
> sip files would be generated and then python bindings from there.  This
> could allow python ( maby even other ) bindings to be built on the fly by
> applications at build time.
>
> Is anyone willing to explore this with me or at least clear me up on what
> those top two macros do in a dcop interface header?  Ideally I want to use
> this with a python engine for KScript, so developers can build native
> python bindings to their applications for automation and extention.
>
> Thanks
> 	-ian reinhart geiser
> - --
>
Perfect, I was looking for something todo during the holiday
Mathieu
-- 
Dare to be naive.
		-- R. Buckminster Fuller

[prev in list] [next in list] [prev in thread] [next in thread]