[Buildbot-devel] VC8 and VC9 errors and lack of logs

[Johnathan Hegge]

On Dec 3, 2010, at 1:03 PM, Rishi Verma wrote:

> Hi Benoit,
> 
> It is odd that I was getting VC8 still, I even checked and double checked the default env and the one being set by buildbot, and VC9 was first in the path with no mention of VC8.  I ended up hardcoding the command with a path.
> 
> I also noticed that the environment for VC9 was not correct.  VC8 included the Platform SDK however, with VC9 this is no longer the case, so I had to make some adjustments accordingly.


I looked at this a bit after I'd seen the first few messages, looking into the Visual Studio classes.  I noticed the default paths for LIB being set in the source with user env appended after.  (I hadn't looked previously as I can't call the solution directly since in my case I use ant wrappers all over to build and manipulate versioning, signing, etc. that I don't want Visual Studio to fiddle with).  

The default builds for each compiler version enforce a pathing that won't work for some builds for sure.   In my case, driver builds depend on more libs from several DDKs and the order of inclusion is sensitive.   Putting the select SDK path first would break my build.  

So, I'd suggest that between the environment setup in a solution/project, the build machines's environment and buildbot's added environment, you'd likely have trouble.    I see the idea of the /useenv to replace an environment but these presumed paths may cause issues as well.  I think less should be specified by buildbot's environment, more passed in or set in the solution.

Try running your build as suggested from Visual Studio command prompt with devenv.com /out <log_file> and catch all the squirrelly output from the compiler/linker to see if it's correct.   This can be different from the output of the individual project .htm log files (if I remember which versions started doing all this...).



> 
> Cheers,
> Rishi
> 
> 
> On Dec 2, 2010, at 12:58 AM, Benoît Allard wrote:
> 
>> Rishi Verma wrote:
>>> Hi All,
>>> I played with this some more and discovered a few things.  Since I had /UseEnv enabled, devenv was choking on it, changing the command to devenv.com fixed that issue and actually produced output for stdio, warnings and errors.
>>> The VC9 builds still seem to fail, setting the command to devenv.com made it easier to figure out, which clearly showed that it was running the wrong version of Visual Studio, it was still running VC8 devenv and therefore could not use my newer solution file.  Any work arounds to the VC9 issue, besides rewriting environment setup step?
>>> Cheers,
>>> Rishi
>> 
>> Hi Rishi,
>> 
>> It looks strange to me that the wrong Visual Studio is being called ... I guess the reason for that is that both directory are in your $PATH, and VC8 at first. Can you figure out why does your VC8 devenv is in your path during the vc9 step ? As the environment setup step for VC9 should only add path that are relative to the VC9 install dir ...
>> 
>> A solution for you though would be to call directly the right devenv, specifying it absolutely.
>> 
>> Regarding the .com/.exe difference, It is the second time in one month I see discussion on this list about that, I'll try to generate a patch soon for that.
>> 
>> Regards,
>> Benoit
> 
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Buildbot-devel mailing list
> Buildbot-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/buildbot-devel