Andrew Borley wrote:
On 3/1/07, Pete Robbins <[EMAIL PROTECTED]> wrote:
I'm just about at a point where I can produce a release candidate which
includes everything except the PHP extension. I'm wondering if it
would be
best to publish this then release the PHP extension as a separate
entity. We
could go the whole hog and release a core package and then separate
packages
for cpp, Ruby, Python, WS binding etc..
Ultimately I think this is the way to go So If I just want to develop in
Ruby and use REST I can download core, Ruby and Rest extensions and not
worry about the others, and more impoortantly, their dependencies.
Any thoughts?
+1 from me. I've had some experience of building the PHP extension and
it's quite a process - you need to build PHP with the right flags,
then download and build a particular branch of the PECL SCA_SDO
package and then you can build the Tuscany PHP extension! (see [1])
It may be worth waiting until the AVOCET branch of the SCA_SDO package
becomes the main downloadable package from the PECL site - I believe
this is the plan for the next SCA_SDO release. This (I think) will
remove (or at least vastly simplify) the first 2 steps in the above
process.
Cheers
Andy
[1]
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/runtime/extensions/php/README
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+1 from me.
If I understand correctly then the Tuscany PHP extension will work with
an actual release of the PECL SCA_SDO package. Correct?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
