[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: RE: Strange Errors, cannot find functions
- From: "Cody Harris" <charris@...>
- Date: Sun, 8 Apr 2007 15:27:07 -0300
Still no luck.
Where should they be defined in the include files?
-----Original Message-----
From: lua-bounces@bazar2.conectiva.com.br [mailto:lua-bounces@bazar2.conectiva.com.br] On Behalf Of David KOENIG
Sent: April 8, 2007 3:04 PM
To: Lua list
Subject: Re: Strange Errors, cannot find functions
Cody Harris wrote:
>
> Hello,
>
> I’ve used Lua before, and I was changing over from VS2003 .NET to
> VS2005. I compiled the .lib file in 2005, and created a new project
> in 2005. I told VS2005 to use the src/ directory as my include
> files. My code is:
>
>
>
> #ifndef _WIN32_WINNT // Allow use of features specific to
> Windows XP or later.
>
> #define _WIN32_WINNT 0x0501 // Change this to the appropriate value
> to target other versions of Windows.
>
> #endif
>
> #include <windows.h>
>
> #include <stdlib.h>
>
> #include <stdio.h>
>
> #include <tchar.h>
>
> extern "C"
>
> {
>
> #include "lua.h"
>
> #include "lauxlib.h"
>
> #include "lualib.h"
>
> }
>
>
>
> int _tmain(int argc, _TCHAR* argv[])
>
> {
>
> lua_State* luaVM ;
>
> luaVM = lua_open();
>
>
>
> lua_baselibopen(luaVM);
>
> lua_strlibopen(luaVM);
>
> lua_mathlibopen(luaVM);
>
>
>
>
>
> My errors are:
>
> Error 1 error C3861: 'lua_baselibopen': identifier
> not found c:\documents and settings\cody harris\my
> documents\visual studio
> 2005\projects\vortexengine\vortexengine\vortexengine\vortexengine.cpp
> 17
>
> Error 2 error C3861: 'lua_strlibopen': identifier
> not found c:\documents and settings\cody harris\my
> documents\visual studio
> 2005\projects\vortexengine\vortexengine\vortexengine\vortexengine.cpp
> 18
>
> Error 3 error C3861: 'lua_mathlibopen': identifier
> not found c:\documents and settings\cody harris\my
> documents\visual studio
> 2005\projects\vortexengine\vortexengine\vortexengine\vortexengine.cpp
> 19
>
>
>
>
>
> Any help is greatly appreciated.
>
>
>
> -Cody Harris
>
I don't know if the MS tools enforce this, but the # signs need to be on
the first column for the preprocessor to get it.
#foo is good
#foo is bad.