Re: can't get luac to build in XCode 2.2.1, OSX 10.4.4?
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: can't get luac to build in XCode 2.2.1, OSX 10.4.4?
- From: Rici Lake <lua@...>
- Date: 2006年1月20日 14:45:41 -0500
On 20-Jan-06, at 2:32 PM, Asko Kauppi wrote:
The _luaP_opnames is a debugging names list, which your library does
not seem to have. You can well live without it, do some grep etc. or
there might even be a #define to ban it.
Actually, it's needed for luac to build; otherwise, luac cannot produce
vm listings.
The symbol is defined in lopcodes.c; in 5.0.2, you must compile with
-DLUA_OPNAMES. This seems to have been simplified in 5.1, but if you're
compiling 5.0.2, take a look at src/luac/Makefile.
The opcode strings occupy a few hundred bytes; except in the very
tightest of embedding environments -- and I don't think Mac OS X would
run on any of those -- it would barely be noticeable :)
jarrod roberson kirjoitti 20.1.2006 kello 20.08:
I have an xcode project that compiles the library code into a dylib
fine, it compiles lua.c against that fine, but I can't get luac to
compile and link correctly.
/usr/bin/ld: Undefined symbols:
_luaP_opnames
collect2: ld returned 1 exit status
/usr/bin/ld: Undefined symbols:
_luaP_opnames
collect2: ld returned 1 exit status
I am compiling everything as C.
--
If you don't know what you want, you probably need a nap.