Re: Linker issue solved; general noob question on the shell...

4 views
Skip to first unread message

Stephan Beal

unread,
Oct 31, 2011, 4:18:31 PM10/31/11
to Norwood, Vode, v8-juic...@googlegroups.com
Hi, Vode! i'm sending this to our mailing list as well...

On Mon, Oct 31, 2011 at 7:48 PM, Norwood, Vode <vodiman...@hp.com> wrote:

I did resolve the linkage issue by setting LD_LIBRARY_PATH temporarily; will resolve same later on

To desired path.


The plugin layer has its own lookup path. See  include/v8/juice/plugin-config.h and look for v8_juice_plugin_CONFIG_PLUGINS_PATH. That gets set by the configure script, but you can of course also edit it by hand (but configure will overwrite it if you run it later on).
 

Am wondering if the v8-juice-shell will supply all the std. functionality of the v8 shell, as built from

The current download + your additional mods?


Good question. See:


for the list of things it has built in. In short, yes, it includes most of my add-on functions and a loadPlugin() function with which to load plugins:


Am a noobie to this and have basic questions; you may

Want to start an “FAQ” on this and stick the basic questions in that faq


You're the first to ask these particular questions, but that possibly just means you're the first one, other than myself, to use these parts. v8-juice-shell is basically just a demo app and an easy way of testing/running the plugins, and is not intended to be one's standard JS shell, and i would be surprised if anyone but me uses it on a regular basis.

i haven't actually touched the v8-juice code in a long time, and prefer to spend my time in the v8-convert code instead. v8-juice is still maintained, in that known problems will be fixed insofar as possible in the current architectural and compatibility constraints, but no major additions/changes to it are planned. v8-convert, on the other hand, is where active development is currently happening:


; as time permits, I’ll be happy to help

Supply docs/writing, as you need it…I tend to document pretty well…


Docs are always good :). Just send them to myself or the list and i'll get them integrated. If integrating them becomes a time problem (or if you think you'll be contributing often) i'll give you write access to the repo and you can check them in yourself.

:)

--
----- stephan beal
http://wanderinghorse.net/home/stephan/
Reply all
Reply to author
Forward
0 new messages