libseed-list SOLVED (Re: something broke with upgrade)



Well, suddenly it went away, after a clean recompile again.. Must have been some old dirt laying around messing things up. Sorry for the noise!

/Jonatan

On 07/13/2010 06:25 PM, Jonatan Liljedahl wrote:
I just recompiled Seed from current git, after upgrading to ubuntu 10.04
and upgrading some gobject-introspection stuff to be able to compile the
latest Seed.

It built fine, but something happened with import.searchPath. With this
file:

// foo.js
print(imports.searchPath);
print(__script_path__);
// EOF

and a modified extensions/Seed.js with debug-prints like this:

print("Running Seed.js");
if(!imports.searchPath || (imports.searchPath.length == 0))
{
print("setting searchPath..");
imports.searchPath = [ "/usr/share/gnome-js",
"/usr/local/lib/seed",
"/usr/local/share/seed",
"/usr/local/lib/seed",
"/usr/local/share/seed",
"/usr/lib/seed",
"/usr/share/seed" ];

if(Seed.argv.length > 1)
{
print("Setting __script_path__");
__script_path__ = GLib.path_get_dirname(Seed.argv[1]);
...

I get this output when running 'seed foo.js':

Running Seed.js
setting searchPath..
Setting __script_path__
/usr/share/gnome-js,/usr/local/lib/seed,/usr/local/share/seed,/usr/local/lib/seed,/usr/local/share/seed,/usr/lib/seed,/usr/share/seed


** (seed:19398): CRITICAL **: Line 2 in foo.js: ReferenceError Can't
find variable: __script_path__

As you see, __script_path__ didn't stick and '.' didn't get added to
searchPath.
Also I noticed that the 'GLib' variable is no longer automatically
available in new contexts as it used to be (since Seed.js exports it as
a toplevel variable). What's going on? This situation breaks the import
system...

/Jonatan
_______________________________________________
libseed-list mailing list
libseed-list gnome org
http://mail.gnome.org/mailman/listinfo/libseed-list



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]