[sldev] Attempting to build 1.23

[Brad Kittenbrink (Brad Linden)]

To my knowledge that shouldn't be necessary, although things may have 
changed recently with recent express versions of visual studio.

Hopefully one of the following links should have the dlls you 
need(depending on your compiler version), but the .libs that reference 
them should have shipped with your visual studio version.
http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=9B2DA534-3E03-4391-8A4D-074B9F2BC1BF&displaylang=en

-Brad

Nexii Malthus wrote:
> Yeah, after some research it seems that .NET Framework SDK 1.1 
> installation is required to get the C Run-Time libraries. (Since my 
> unstable connection makes it absolutely impossible to download the 
> newer platform SDK which is 1GB, so I had to find alternative ways 
> that don't require downloading 1GB off a slow microsoft server)
>
> Ugh, the .NET SDK is 100mb, that doesn't help much either..
> Gotta hate the way microsoft does things.
>
> On Tue, Jun 16, 2009 at 7:24 PM, Nexii Malthus <nexiim at googlemail.com 
> <mailto:nexiim at googlemail.com>> wrote:
>
>     Ahhh! Thank you so much, that explains it.
>
>     It seems my copy of the windows platform SDK (Microsoft Platform
>     SDK for Windows Server 2003 R2) doesn't have msvcrt.lib in the Lib
>     folder, instead msvcrt.lib is only offered in the folders for the
>     different architectures. Odd.
>
>     -Nexii Malthus
>
>
>
>     On Tue, Jun 16, 2009 at 4:30 PM, Brad Kittenbrink (Brad Linden)
>     <brad at lindenlab.com <mailto:brad at lindenlab.com>> wrote:
>
>         Google-perftools is intentionally not enabled in 1.23, but all
>         of our other 3rd party libraries were rebuilt in preparation
>         for it (or some other memory allocator that we may settle on
>         in the future).  So all of our library packages were replaced.
>
>         We had been linking statically to the Microsoft C Runtime
>         Library, but now we are linking dynamically.
>
>         From your error messages it appears that this is your problem,
>         it's failing to find symbols that are defined in the C Runtime
>         Library, and it's warning that symbols imported from a dll are
>         also defined inline.  This likely means that some .obj files
>         have not been rebuilt that need to be, and are still referring
>         to the static CRT library.
>
>         If you're building any 3rd party libs yourself, you will need
>         to have this option (/MD) selected for all code linked into
>         the viewer binary (it's under C++->Code Generation).  
>         If you're using our library packages specified in install.xml
>         and downloaded automatically by cmake, then this should all
>         "just work". Additionally you should make sure you're building
>         from a clean checkout.
>
>         Let me know if this doesn't fix it for you.
>
>         -Brad
>
>
>         Nexii Malthus wrote:
>
>             Is Google Performance Tools library the culprit here? I
>             can't seem to
>             find a linker to it in my solution, neither does it appear
>             in the
>             install.xml/installed.xml. But there is a mention of the
>             google-perftools license in the
>             LICENSE-libraries-win32.txt file. Was
>             this added recently and accidentally left out in the cmake
>             files?
>
>             On 6/16/09, Nexii Malthus <nexiim at googlemail.com
>             <mailto:nexiim at googlemail.com>> wrote:
>              
>
>                 I'm getting a lot of external symbol errors, what
>                 libraries have been
>                 changed in 1.23 after moving from 1.22?
>
>                 I have run cmake and all perfectly fine but it seems
>                 like I must be
>                 missing some additional libraries or my libraries are
>                 older versions.
>                 I have compiled the 1.22 client perfectly fine before
>                 but 1.23.4 has
>                 stumped me. I'm unable to find any references on the
>                 wiki and I am
>                 frankly just getting frustrated. Being able to compile
>                 1.23 would help
>                 me find the origin of mysterious crashes that occur on
>                 me with the
>                 official client, as well as update my custom client to
>                 the new
>                 codebase.
>
>                 For a full error list see the attachment in this forum
>                 post:
>                 http://nexii.ordoimperialis.com/viewtopic.php?f=4&t=58
>                 <http://nexii.ordoimperialis.com/viewtopic.php?f=4&t=58>
>
>                 I have exhausted most of my options and a friend
>                 suggested it might be
>                 that this is a library issue.
>
>                    
>
>             _______________________________________________
>             Policies and (un)subscribe information available here:
>             http://wiki.secondlife.com/wiki/SLDev
>             Please read the policies before posting to keep
>             unmoderated posting privileges
>              
>
>
>
>