SV: [sldev] Unresolved externals

Soft soft at lindenlab.com
Fri Jul 18 07:15:06 PDT 2008


On Fri, Jul 18, 2008 at 8:47 AM, Suzhanna Rossini
<suzhanna.rossini at balsaestates.com> wrote:
>> [snip]
>> > >
>> > > Coming to think of it.. Would there be any point for me to install
>> > VS2005? I
>> > > can use my friends license since he's moved completely to VS2008
>> and
>> > only
>> > > keeps VS2003 for special occasions.
>> > > The only package I have myself is VS2008, and that seems to be a
>> lot
>> > more
>> > > "unsafe" judging from discussions here and elsewhere.
>> > >
>> > > I also came to think of llkdu.dll, it seems like that isn't copied
>> to
>> > the
>> > > right place by unpacking the libraries and pulling the SVN
>> sources..
>> > Neither
>> > > does it seem to be built in the process, if I don't copy it
>> manually,
>> > I get
>> > > a copy error from the VS2003 solution.
>> >
>> > I don't think switching to VS2005 will make a difference. I just
>> > finished a VS2003 build and I don't have the problem there either. I
>> > also ran a cygwin setup update to ensure that nothing bad had crept
>> > into cygwin recently.
>> >
>> > The function that your linker isn't finding is in lex_yy.cpp. Try
>> > adding an "#error I got here" before this function in lex_yy.cpp,
>> just
>> > to rule out some preprocessor difference that's making the code
>> > unreachable. It's possible you're inheriting a strange #define from
>> > somewhere:
>> >
>> > BOOL lscript_compile(const char* src_filename, const char*
>> > dst_filename,
>> >                                      const char*
>> > err_filename, BOOL is_god_like)
>> >
>> >
>> > Regarding llkdu - that's currently provided for release candidate
>> > builds only. There are still some sticky issues attached to that. For
>> > the time being, you can remove the three llkdu rules from
>> > copy_win_libs and the viewer will use openjpeg if llkdu isn't
>> present.
>> > Again though, this should have nothing to do with your link error.
>>
>>
>> Uh oh... I don't even have a file lex_yy.cpp on disk!
>
> I found the function in
> C:\SLDev\release\indra\build-VS2003\lscript\lscript_compile\indra.l.cpp
> though.. I'll add it there to check.

Oops - lex_yy.cpp was the old pre-cmake name. indra.l.cpp is the
current name. indra.l.cpp is indeed the file you would check.


More information about the SLDev mailing list