SV: [sldev] Building with VS2008?

Suzhanna Rossini suzhanna.rossini at balsaestates.com
Tue Jul 1 10:28:16 PDT 2008


> You will run into many problems with Visual Studio 2008 and the
> current release candidate viewer (1.20). Visual Studio 2003 is the
> only officially supported Windows compiler there.
> 
> Things will be much easier if you pull the release branch and use
> cmake, which can generate Visual Studio 2008 project files.


Okay... I tried that, but I used the pre-built libraries from 1.20 Viewer-2 r90229.
Seems like most compiled clean enough, some warnings here and there, but I also got a list of errors while linking.

llcompilequeue.obj : error LNK2019: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H at Z) referenced in function "protected: void __thiscall LLFloaterCompileQueue::compile(char const *,class LLUUID const &)" (?compile at LLFloaterCompileQueue@@IAEXPBDABVLLUUID@@@Z)
llpreviewscript.obj : error LNK2001: unresolved external symbol "int __cdecl lscript_compile(char const *,char const *,char const *,int)" (?lscript_compile@@YAHPBD00H at Z)
aprutil-1.lib(open.obj) : error LNK2019: unresolved external symbol __imp__wcscpy referenced in function _utf8_to_unicode_path
aprutil-1.lib(filesys.obj) : error LNK2001: unresolved external symbol __imp__wcscpy
aprutil-1.lib(dir.obj) : error LNK2001: unresolved external symbol __imp__wcscpy
aprutil-1.lib(apr_snprintf.obj) : error LNK2019: unresolved external symbol __imp__modf referenced in function _apr_cvt
aprutil-1.lib(proc.obj) : error LNK2019: unresolved external symbol __imp__wcschr referenced in function _apr_proc_create at 24
aprutil-1.lib(dir.obj) : error LNK2001: unresolved external symbol __imp__wcschr
aprutil-1.lib(sockaddr.obj) : error LNK2019: unresolved external symbol __imp__strspn referenced in function _find_addresses
aprutil-1.lib(pipe.obj) : error LNK2019: unresolved external symbol __imp__getpid referenced in function _apr_create_nt_pipe
OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp__getpid
OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp___getpid
aprutil-1.lib(start.obj) : error LNK2019: unresolved external symbol __imp____p__wenviron referenced in function _apr_app_initialize at 12
aprutil-1.lib(start.obj) : error LNK2019: unresolved external symbol __imp____p__environ referenced in function _apr_app_initialize at 12

aprutil-1.lib(start.obj) : error LNK2019: unresolved external symbol __imp____p__wenviron referenced in function _apr_app_initialize at 12
aprutil-1.lib(start.obj) : error LNK2019: unresolved external symbol __imp____p__environ referenced in function _apr_app_initialize at 12
aprutil-1.lib(open.obj) : error LNK2019: unresolved external symbol __imp__wcscpy referenced in function _utf8_to_unicode_path
aprutil-1.lib(dir.obj) : error LNK2001: unresolved external symbol __imp__wcscpy
aprutil-1.lib(filesys.obj) : error LNK2001: unresolved external symbol __imp__wcscpy
aprutil-1.lib(dir.obj) : error LNK2019: unresolved external symbol __imp__wcschr referenced in function _apr_dir_read at 12
aprutil-1.lib(proc.obj) : error LNK2001: unresolved external symbol __imp__wcschr
aprutil-1.lib(apr_snprintf.obj) : error LNK2019: unresolved external symbol __imp__modf referenced in function _apr_cvt
aprutil-1.lib(sockaddr.obj) : error LNK2019: unresolved external symbol __imp__strspn referenced in function _find_addresses
aprutil-1.lib(pipe.obj) : error LNK2019: unresolved external symbol __imp__getpid referenced in function _apr_create_nt_pipe
OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp__getpid
OLDNAMES.lib(getpid.obi) : error LNK2001: unresolved external symbol __imp___getpid

To me, at a glance, it looks like it's the Apache libraries that gives the errors, so I guess I'll rebuild them and see if things get better.. Or am I on the wrong track?




> 
> 
> On Mon, Jun 30, 2008 at 2:54 PM, Suzhanna Rossini
> <suzhanna.rossini at balsaestates.com> wrote:
> > I'm struggling to build the client with VS2008, but I'm running into
> a whole
> > lot of obstacles.
> > Is there anybody out there that can give pointers and advice? I'm
> rather new
> > to the Windows way of doing things, and VS2008 is the only
> environment I
> > have available.
> >
> > Thank you!
> > _______________________________________________
> > Policies and (un)subscribe information available here:
> > http://wiki.secondlife.com/wiki/SLDev
> > Please read the policies before posting to keep unmoderated posting
> > privileges
> >



More information about the SLDev mailing list