[opensource-dev] autobuild with VS2005

Marine Kelley marinekelley at gmail.com
Mon Apr 18 12:01:45 PDT 2011


Thanks... this convinces me to go with VCE2010 (getting over the
initial gripe I have about it, since it is the only sensible option I
have to go ahead anyway).

Right now it builds to the end, but it fails at the very last step
with this error :

60>  Looking for existing VisualStudio instance...
60>    Didn't find open solution, starting new background VisualStudio
instance...
60>    Reading .sln file version...
60>    Using version: VC100...
60>  Value cannot be null.
60>  Parameter : type

Seems to be vstool complaining that it cannot find the instance of VS
when calling GetDTEAndSolution() in main.cs... although VCE is open.
Autobuild does that too on the command line. What can I do to make it
find VCE and modify the solution ? I'm thinking some path is missing
from my PATH env variable but I can't figure out which.

Thanks again


On 18/04/2011, Ima Mechanique <ima.mechanique at blueyonder.co.uk> wrote:
>> Thank you all for the pointers.
>>
>> So if I get this right, VS2005 is to be left behind... not really kind
>> to people who are used to it, and who find 2010 to be an unbearable
>> bloatware that runs 4x slower than the old IDE. Not mentioning that
>> with 2005, at least I could do something else while compiling. With
>> this one, I can do something else... as long as it's away from my
>> computer.
>
> Not so much that 2005 is being left behind, but that LL is moving
> forward. They cannot stay with the same environment when the Operating
> Systems are moving forward; for many reasons.
> How fast VC10 runs depends a LOT on your system and configuration. When
> I first used autobuild with it, it took the same time to build the
> viewer as 2005 had (approximately) However this turned out to be because
> I was not using some of the optimisations possible that 2005 had been
> using. With these enabled, it is now 35 minutes faster than 2005.  Yes,
> it is a resource hog, but that's how it gets to be faster, you can
> change default values to prevent that if you want to, I make a cup of
> coffee and do something else ;-) Also, autobuild is designed to use the
> command line, not the IDE which is a great part of the resource eating.
> Intellisense is a pain in the ... RAM, disc I/O, etc. for example.
>
> As has been said already, autobuild started on the 2005 build, if you
> want to continue using it you will need to collect all the 2005 build
> versions of the libraries and create a configuration file that uses them
> instead of the default one which uses 2010 builds.
>
> If you are using the Express version of 2005 you will probably have to
> do more to get it to work. The initial version of autobuild was not
> express friendly. This is caused by many differences in how the
> full/express versions work.
>
> Start with the repo at https://bitbucket.org/oz_linden/viewer-autobuild/
>
> That is the one started for 2005 builds, so should contain some if not
> all the library links  I have no idea if those files are still available
> from the amazon servers though.Be aware it is considerably out of date
> with the main code base now, so you will have to import from
> viewer-development, being careful not to over write the autobuild.xml,
> best to rename it.
>
>> And if I also get this right, "VCexpressRelWithDebInfo" is the only
>> configuration that I should use, isn't it ? I am told to always use
>> the "OpenSource" ones, except if I am on Windows (which is the case).
>> Doesn't matter, I'll try both.
>
> IIRC the OpenSource* configurations are for full versions of VC only.
> They may work with a full version of 2005.
> VCexpressRelWithDebInfo is for VC10 Express versions. It uses commands
> not available on 2005, so probably will not work at all for you.
>
> --
> Ima Mechanique
> ima.mechanique(at)blueyonder.co.uk
>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>


More information about the opensource-dev mailing list