installing valentina xcmd

[Yennie at aol.com]

I don't know if this will make a difference, but you could try changing the 
path to:

./myExternal.bundle

It really shouldn't make a difference, but that's what I've used before.
You can also bury it in a relative folder such as:

./externals/myExternal.bundle

Finally, one last technique. Create an external "library" stack, set the 
externals property of that stack, and "start using" the library stack. This gives 
you finer control of when the external is actually loaded. It's also nice 
because you can still make changes to the library stack without rebuilding the 
standalone, including wrappers to external calls, etc.

When the external isn't working, what do you find when you query the 
"externalFunctions" property? Do you get "Valentina" in the list?

Also, is there any way you could be changing the current directory before the 
external is loaded (which I think is impossible unless you use "start using", 
but alas...)? Reason I ask is because the external property is a relative 
path. You might try outputting the current directory when the external is not 
working, and see if it is something other than the path to the application.

Hope something there helps!

> I was wondering if my filepath for the OS X external is correct though.
> I use simply "myExternal.bundle" and the external is placed in the same
> folder as the app (which is itself a bundle.) This gives variable
> results. Since the Macho engine is inside the Resources folder, which is
> inside the Contents folder, I tried putting the external.bundle into the
> Resources folder inside the app bundle. Still no go.
> 





------------------------------
Brian Yennie
Chief Technology Officer
QLD Learning, LLC
www.QLDLearning.com

PH: (904)-997-0212
EMAIL: Yennie at aol.com
-------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.runrev.com/pipermail/use-livecode/attachments/20030616/16141a17/attachment.html>