[sldev] Building 1.19.1

[Tony]

Ok, I'm going to bring this back to the list since it was my mistake in 
forgetting to include the list earlier. I am compiling under ReleaseNoOpt

Thanks Scott for pointing out where the artwork download was. In source 
column, my eyes didn't even read down past Windows, thinking that the 
other links were for other OSes.
Also, Mike's suggestion to comment out the #define SAFE_SSL 1 in llcurl 
got rid of the openssl file issue. (though I did find the file in my 
cygwin/usr/include directory. I just don't know how to incoporate it 
properly.)

I have one error left, and that is regarding unistd.h. I have added my 
cygwin/usr/include path (where I found a version of the file) to my 
libraries for projects, but that didn't seem to solve it.
I could copy it over, but I'm not sure if that's the right action (I 
also found a few other copies of that file in different cygwin directories).

I do have a few warnings as well. I'm not sure if they will actually 
cause me any problems, but I thought I'd mention them in case someone 
knows I'm headed for trouble.
There are a number of 
warning LNK4221: no public symbols found; archive member will be 
inaccessible    llrect.obj
for a couple of files (llrect and lllogitechlcd) as well as llmozlib2. 
Now I remember seeing something about not compiling llmozlib with VS 
2005, but I have a feeling that will make my testing difficult as I will 
be testing some of the new HTML feed vs video features.

I also have a number of the following:

Warning    8    warning LNK4099: PDB 'apr_src.pdb' was not found with 
'../../libraries/i686-win32/lib_release\apr-1.lib' or at 
'd:\slv_1_19_1_0\linden\indra\win_crash_logger\apr_src.pdb'; linking 
object as if no debug info    apr-1.lib

I'm not too worried about that one though since some parts of the wiki 
mention unloading it and the win_updater (and removing them as 
dependencies) anyways.

Thanks everyone for all your help so far!

Tony


Scott Squires wrote:
> On Mon, 10 Mar 2008 09:44:17 -0700, Tony <anthonyrbundy at gmail.com> wrote:
>   
>> Are the .pdb files generated solely by VS? Is there no information
>> contained in them that it can't get from the rest? If so, I'll just
>> delete the file and try to recompile to see if that fixes the issue.
>>     
>
> Yeah, .pdb files are debugging information files generated by visual
> studio.  Which reminds me to ask, what build target did you choose? 
> ReleaseNoOpt or ReleaseForDownload are the ones to go with, I don't think
> that the Debug target will compile.  This is something I often forget to do
> when I am doing a fresh compile, even though I know it won't work on Debug.
>  I have noticed severe graphics bottlenecks with ReleaseNoOpt, probably due
> to the opengl error checking it does (30+ fps on ReleaseForDownload, less
> than 10 fps on ReleaseNoOpt).  So I would only use ReleaseNoOpt for
> debugging.
>
>   
>> I did install cygwin, though I did have some problems. I had to exclude
>> installing gnupg from the install because the install would crash
>> everytime it got to that portion. I also made sure that bison, flex and
>> pathutils were included in the install. Maybe there are more that I need
>> to check?
>>     
>
> The lex_yy.cpp I think is supposed to be the output of bison.  So it sounds
> like bison failed.  Look through the build output to see if you can find
> anything about bison.  Some people on MacOS were having trouble with a
> particular version of bison generating a file with a different name than
> the build scripts expected.
>
> Mike commented about the openssl thing, it sounds like that may be a
> problem with the source, I'd try his suggestion of commenting out the
> offending line (see his post on the list).
>
>   
>> I did find several different unistd.h and a crypto.h in the cygwin
>> install, should I just copy one of them over? (any one in particular?)
>> or does that need to happen as part of the build process?
>>     
>
> Try commenting out the line that Mike referred to and see if that helps.
>
>   
>> Should this location be added to the libraries directories for the
>> solution?
>>     
>
> I haven't ever had to add library paths, but I used the community-provided
> solution files.
>
>   
>> I downloaded both the source and libraries from
>> https://wiki.secondlife.com/wiki/Source_downloads.links for 1.19.1.0
>> I unzipped the libraries into the same folder as the program source
>> Is there another location with the artwork separate from the program
>> source that I need to get? I don't remember seeing anything about that
>> in the wiki instructions.
>>     
>
> If you look at the page:
>
> https://wiki.secondlife.com/wiki/Source_downloads#ver_RC-1.19.1.0
>
> In the source column there are win/mac/linux downloads, and then also an
> "artwork" link.  You need to download that and extract it into the source
> directory like you did with the libraries.
>
> Good luck!  That's about as much as I know, hopefully it will get you past
> some of the issues anyway.  =)
>
> --Scott
>
>
>