Installation instructions are missing a step

[engstrom]

To install the extension in Chrome I had to move the js files into the Chrome folder since all of the paths in the manifest file are relative.

[honestbleeps]

You're supposed to run the make links script actually.
On Jan 3, 2014 9:36 PM, "Dustin Engstrom" [email protected] wrote:

To install the extension in Chrome I had to move the js files into the
Chrome folder since all of the paths in the manifest file are relative.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2
.

[engstrom]

My bad. I skipped straight to the "Instructions for loading/testing" section and missed that.

[wormeyman]

I ran the make links script and I think the /lib/modules folder needs to be added to it?

[honestbleeps]

makelinks.sh should hardlink all files from lib/* and lib/modules/* to each browser's directory -- note that there's an update to makelinks.sh i made recently because of the new split... I copied it over from RES, though, so it's possible it needs an edit or two, I'll try and test later!

[wormeyman]

I used the bat file since i am on windows, i'll take a look at the sh and see if i can understand it.

[honestbleeps]

ahh, sorry, I haven't updated the bat file yet -- you're right, those files need to be added... or ideally I should re-jog my memory on doing more worthwhile things with BAT files (I'm sure I can replicate the way makelinks.sh works)... I just haven't had time.. my apologies for the confusion!

[wormeyman]

Take a look at my pull request for the bat, Just be aware that i have not tested it on anything but chrome. Also on the bat file what is the files=() for at the top?