endflow.net blog

/* Introduction */

I have build SpiderMonkey 1.7.0 on Windows XP SP2 using Visual C++ 2008 (Visual Studio 2008 Command Prompt). However, I couldn’t build easily because I encountered some linker errors. So I would like to describe about how to avoid errors.

/* Build Requirements */

I don’t know enough or not.

• SpiderMonkey 1.7.0 Source code
• Visual C++ 2008 (Visual Studio 2008 Command Prompt)

I use Development Edition but maybe you can do this using Express Edition.

/* Failed Building */

There are many build targets.

"js - Win32 Release" (based on "Win32 (x86) Dynamic-Link Library")
"js - Win32 Debug" (based on "Win32 (x86) Dynamic-Link Library")
"jsshell - Win32 Release" (based on "Win32 (x86) Console Application")
"jsshell - Win32 Debug" (based on "Win32 (x86) Console Application")
"jskwgen - Win32 Release" (based on "Win32 (x86) Static Library")
"jskwgen - Win32 Debug" (based on "Win32 (x86) Static Library")
"fdlibm - Win32 Release" (based on "Win32 (x86) Static Library")
"fdlibm - Win32 Debug" (based on "Win32 (x86) Static Library")

*part of js.mak

In this entry, I decide to use “jsshell – Win32 Debug”. Because I want to check DLL(js32.dll) quickly with the console application “JSShell”(jsshell.exe).

OK, let’s execute following build command from Visual Studio 2008 Command Prompt.

nmake -f "js.mak" CFG="jsshell - Win32 Debug"

After executing, you will get many many “Warning” messages and few “Error” messages and fail to build. First, focus on Error messages (ignore Warning messages in this time),

jsapi.obj : error LNK2001: unresolved external symbol "_js_GeneratorClass"
jsapi.obj : error LNK2001: unresolved external symbol "_js_IteratorClass"
jsapi.obj : error LNK2001: unresolved external symbol "_js_StopIterationClass"
jsapi.obj : error LNK2001: unresolved external symbol "_js_InitIteratorClasses"
jsobj.obj : error LNK2001: unresolved external symbol "_js_InitIteratorClasses"
jsgc.obj : error LNK2019: unresolved external symbol _js_CloseGeneratorObject referenced in function _js_RunCloseHooks
jsgc.obj : error LNK2019: unresolved external symbol _js_CloseIteratorState referenced in function _CloseIteratorStates
jsinterp.obj : error LNK2019: unresolved external symbol _js_NewGenerator referenced in function _js_Interpret
jsinterp.obj : error LNK2019: unresolved external symbol _js_CloseNativeIterator referenced in function _js_Interpret
jsinterp.obj : error LNK2019: unresolved external symbol _js_CallIteratorNext referenced in function _js_Interpret
jsinterp.obj : error LNK2019: unresolved external symbol _js_ValueToIterator referenced in function _js_Interpret

like this.

/* Fix Makefile */

As you know, there are linker errors. When I hear “linker error” and “unresolved”, I remember “library” problem, but in this time, it has different problem. Because the missing symbol has prefix “_js_”.

Next, I think the code excluded by pre-processor such as “#ifdef” and “#endif”. However, I couldn’t find doubtful codes. There is the missing function “js_CallIteratorNext” in jsiter.c (extern declaration in jsiter.h).

Erm … next, I think I grep object files and check the name of missing symbol. When just I saw the list of object files in Explorer, I understand causes of build error. Surprisingly, there are no describe of “jsiter”(jsiter.h, jsiter.c, jsiter.obj)! That’s mean the object file “jsiter.obj” (include symbol “js_CallIteratorNext”) didn’t generated.

I got causes and I would like to add jsiter.* into Makefile(js.mak). However, it is annoying work. So I put modified Makefile in here(as you know, UNWARRANTABLE).

/* Succeed Building */

The fix was done, let’s try re-build. For safety, I recommend to delete “Debug” directory completely. The build will succeed and generated “js32.dll” and “jsshell.exe” in Debug directory. (there are many many warning as usual)

Hum … why don’t I use Tamarin? lololol

enjoy JS with SpiderMonkey!