Pete Robbins wrote:
Yes it does help! I need to go and read the Assembly spec again ;0)
But for now I think the change I put in is fine.
Cheers,
Pete,
I thought that your change was OK too, but I just rebuilt everything
after updating from SVN and unfortunately this change breaks the Ruby
extension. Sorry I should have detected this before... but line 75 of
RubyImplementation.cpp needs the root directory of the composite to find
the Ruby script, as most people will specify a path to the script file
relative to the .composite file in <implementation.ruby script="..."/>.
The Ruby extension hits what I was trying to describe earlier in this
thread. Implementation artifacts are packaged with the composite, so
they need to know which composite they are packaged in, the current
directory etc. The Python and PHP extensions probably do not run into
this because they don't look at the script until the first invoke (and
are passed the composite at that point), but they will run into this as
soon as they try to read and introspect a script earlier in the load
sequence.
So right now the Ruby extension is broken by this change. To build on
Linux without it, use configure --enable-ruby=no.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
