Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

How to link to spidermonkey?

  • 1 réponse
  • 2 ont ce problème
  • 23 vues
  • Dernière réponse par 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

Solution choisie

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.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

more options

Solution choisie

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.