#33 -L for library search path

[Richard Uhler]

esiply should take a command line switch -L which gives a path to look for library files in. You should be able to specify multiple paths. And there should be some default ones, like where the libs were originally installed.

[Richard Uhler]

Logged In: YES
user_id=1884147
Originator: YES

This requires an addition to ESNI as a way to specify a path, doesn't it? Perhaps there can be an Esiply.libpaths array which is a list of the files to look at? Then we could use ESNI's evaluate function.

But is that really what Esiply is for? No, I think that needs to be an ESNI feature, as ESNI is all about the modular stuff, right?

[Richard Uhler]

Logged In: YES
user_id=1884147
Originator: YES

Ahh, I know. We're going to need an ESNI exposed to the javascript in order to load the libraries from javascript. That might look like:

ESNI.load("foo");

Where the load looks up in the ESNI.libpaths array.
Now pass -L values directly to ESNI.libpaths. Easy.

[Richard Uhler]

Logged In: YES
user_id=1884147
Originator: YES

Except we now have a problem. How can javascript be run before the standard libraries are installed, and how can we know where to find the javascript libraries without running the javascript to specify them?

Perhaps at this point it would be best just to find a temporary solution to the make check bug. We could, for example, pass a single char* pointer to esni_create which is the location of the standard libraries. In the future maybe it will be more obvious how to correctly fix the problem.

[Richard Uhler]

Logged In: YES
user_id=1884147
Originator: YES

I made the hackish change with revision 48.

Keeping the bug around, however, because it has yet to be fixed properly.