Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

How to link to spidermonkey?

  • 1 vastaus
  • 2 henkilöllä on sama ongelma
  • 2 näyttöä
  • Viimeisin kirjoittaja Paul

more options

I would like to post [this question](http://stackoverflow.com/q/32328960/719276 ) on a mozilla forum, this is the best forum I found.

I successfully [compiled spidermonkey](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Build_Documentation) (on windows), how can I link against it now (to [embed it](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/How_to_embed_the_JavaScript_engine))?

[js-config](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Build_Documentation#Using_the_js-config_script) is not properly installed, and I don't understand [this workaround](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Releases/1.8.5#js-config). Linking to the static library should be easier, but I don't even know which file it is. I have `mozglue.lib, mozjs-43a1.lib, nspr4.lib, plc4.lib, plds4.lib` in `dist/sdk/lib` and `nspr4.lib, plc4.lib, plds4.lib` in `dist/lib`.

      • Notes***
  • I used the following command to compile:*
   g++ -std=c++11 -I<objdir>/dist/include -L<objdir>/dist/lib helloworld.cpp -o helloworld  -lmozjs-31 -lz -lpthread -ldl 
  • I know it is not the correct way to compile it since those libraries are not in `<objdir>/dist/lib`. It returns the following errors:*
   [...]/jscpucfg.h:121:3: erreur:
   #error "Cannot determine endianness of your platform. Please add support to jscpucfg.h."
   [...]
   erreur: ‘JS_EvaluateScript’ was not declared in this scope
I would like to post [this question](http://stackoverflow.com/q/32328960/719276 ) on a mozilla forum, this is the best forum I found. I successfully [compiled spidermonkey](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Build_Documentation) (on windows), how can I link against it now (to [embed it](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/How_to_embed_the_JavaScript_engine))? [js-config](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Build_Documentation#Using_the_js-config_script) is not properly installed, and I don't understand [this workaround](https://developer.mozilla.org/en-US/docs/Mozilla/Projects/SpiderMonkey/Releases/1.8.5#js-config). Linking to the static library should be easier, but I don't even know which file it is. I have `mozglue.lib, mozjs-43a1.lib, nspr4.lib, plc4.lib, plds4.lib` in `dist/sdk/lib` and `nspr4.lib, plc4.lib, plds4.lib` in `dist/lib`. ***Notes*** *I used the following command to compile:* g++ -std=c++11 -I<objdir>/dist/include -L<objdir>/dist/lib helloworld.cpp -o helloworld -lmozjs-31 -lz -lpthread -ldl *I know it is not the correct way to compile it since those libraries are not in `<objdir>/dist/lib`. It returns the following errors:* [...]/jscpucfg.h:121:3: erreur: #error "Cannot determine endianness of your platform. Please add support to jscpucfg.h." [...] erreur: ‘JS_EvaluateScript’ was not declared in this scope

Valittu ratkaisu

Hi

Your issue seems a bit more complicated and requires more investigation. We're currently looking into it and we'll get back to you with more details ASAP. Please understand that escalations can take up to 72 hours for a response, but no longer.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (1)

more options

Valittu ratkaisu

Hi

Your issue seems a bit more complicated and requires more investigation. We're currently looking into it and we'll get back to you with more details ASAP. Please understand that escalations can take up to 72 hours for a response, but no longer.