What's GLUEscript?

GLUEscript (Glueing Libraries Using EcmaScript) is the successor of wxJavaScript. The new name covers the goal of this project: create a JavaScript engine which can be used as a general purpose language (like Perl for instance).

Read the history behind GLUEscript.

GLUEscript is developed by Franky Braem


GLUEscript uses SpiderMonkey, the JavaScript engine used in FireFox.


Portable Code

GLUEscript is written in portable C++ code. GLUEscript uses PoCo, a library for writing portable C++ code. And wxWidgets is used as GUI toolset. The GUI glue is optional.

Powered by POCO
Built with wxWidgets

GLUEscript uses Premake for generating makefiles for gcc, project files for Visual C++, CodeLite, Code::Blocks, ... Premake can be used on Windows, Linux and MacOS.


A new logo

Anoop Kumar Narayanan donated a new logo for GLUEscript. Thanks!

GLUEscript 0.1.04 released

This is the changelog:

  • Wrong line number reported on error on Windows
  • JS_C_STRINGS_ARE_UTF8 is not needed anymore, JS_CStringsAreUTF8 is called.
  • Windows: NSPR not included anymore because this resulted in a crash with Apache. NSPR must be build first, before building PocoSpiderMonkey.
  • Switch back to SpiderMonkey 1.8.0 on Windows: latest code (which wasn't released yet is not bug free). Make it possible to build GLUEscript with the latest and 1.8.0 (defines GLUE_JS_180).

Powered By Mozilla

GLUEscript is now officially powered by Mozilla: look at http://www.mozilla.org/projects/powered-by.html

GLUEscript 0.1.03 released

Release 0.1.03 contains a fix when a context is created: JSOPTION_VAROBJFIX is removed because it results in errors in "include" method.

GLUEscript 0.1.02 released

Today a new version of GLUEscript is released. The major change is that now GLUEscript runs on Linux 64-bit (Ubuntu).

For Linux 32-bit do the following: download the SpiderMonkey library and configure it (enable threading). Copy jsautocfg.h, js-confdefs.h and js-config.h to gluescript\src\Poco\Script\JavaScript\SpiderMonkey\src\js\cfg\linux32. Add the following to common.lua:

  configuration { "linux", "x32" }
    includedirs { 

GLUEscript on Linux

For those who want to run GLUEscript on Linux: I'm currently doing a lot of work to make it build on Linux. The article "Don't waste your time on GLUEscript" made me realize that GLUEscript wasn't ready for Linux. Allthough I always released an archive with the source code targeted to Linux, it was difficult to get GLUEscript run on it. I'm polishing up the code now, and I hope to release a source archive that builds on Linux soon. Stay tuned.

If you can't wait, you can always clone the git repository and give it a try.

Don't waste your time on GLUEscript

Today I've stumbled upon an article "Don't waste your time on GLUEscript" written by Eugene Reimer.

This is my answer on his story: Why in the first place do I open my source code to the open source community? I hope it can be useful for other developers, users, ... around the world. Developers are free to use the code, change the code and contribute to the project. Do I have the knowledge of every single platform? No I don't and that's where I hope the open source community steps in and tries to help on the project. And some people do: "installing GLUEscript on debian squeeze 64bit". When I have a problem on the Poco library, I don't start a thread on my website and shout that Poco doesn't work: No, I try to share my problem on the forum or I try to solve the problem myself and share it with the Poco project members. That's the greatest thing about open source: If you can't solve it, maybe someone else can.

I know GLUEscript is not finished (will it ever?), but instead of ranting about the problems, Eugene could have send me a mail, entered a bug-report or mentioned the problems on the google group to make GLUEscript better. And for someone who knows every programming language, except Basic, it can't be a problem to dig in the code.

Every line of code in GLUEscript is written during spare-time. A blog-entry like this feels like a dagger in the back.

If you wish you can also discuss this topic in the Google group.

Integrated NSPR and SpiderMonkey

In the next version the NSPR and SpiderMonkey library will be integrated in the Poco SpiderMonkey library. This was possible by JSMiniNSPR and the packaging-spidermonkey project on code.google.com. At the moment this is only for the Windows version. I don't know yet if the same approach will be used on Linux.



Thanks to SmartGit the move to Git went smoothly. I'm a developer for about 20 years now, and I know how to use the command-line, but when a GUI is available to reduce the work you need to do ... My first experiments with Git were no success. I've tried msysgit, but it was after using SmartGit that I was convinced to move to Git. I used SmartSVN in the past to work with Subversion on Linux, and SmartGit works in the same way. SmartGit is available for Windows, Linux and Mac OS X.

Moving to Git

The development of the next version will be done with Git as version control system. I still have to learn a lot about Git, but SmartGit is a great tool and makes it possible to use Git like I did with SubVersion.

Syndicate content