Re: [C++] Extension mechanism and the REST binding

2007-01-24 Thread Pete Robbins
On 23/01/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Pete Robbins wrote: Actually this is definitely a problem. The mechanism as it is today means you can not have one extension library that depends on another unless we separate out the static method into it's own dll for each

[C++] Extension mechanism and the REST binding

2007-01-23 Thread Pete Robbins
I've run in to a problem building the REST binding extension on MacOS. Our extension mechanism works by having a well known exported method from a library that implements an extension; tuscany_sca_extension_initialize() In the REST binding the extension is split into interface, service,

Re: [C++] Extension mechanism and the REST binding

2007-01-23 Thread Pete Robbins
This seems to build fine on linux and does not warn about the duplicate symbol. I'll go back and check why Mac is complaining. Cheers, On 23/01/07, Pete Robbins [EMAIL PROTECTED] wrote: I've run in to a problem building the REST binding extension on MacOS. Our extension mechanism works by

Re: [C++] Extension mechanism and the REST binding

2007-01-23 Thread Pete Robbins
Actually this is definitely a problem. The mechanism as it is today means you can not have one extension library that depends on another unless we separate out the static method into it's own dll for each extension. It may work on Linux but it probably shouldn't and it will not work on MacOS. So

Re: [C++] Extension mechanism and the REST binding

2007-01-23 Thread Jean-Sebastien Delfino
Pete Robbins wrote: Actually this is definitely a problem. The mechanism as it is today means you can not have one extension library that depends on another unless we separate out the static method into it's own dll for each extension. It may work on Linux but it probably shouldn't and it will