[Scons-users] How to build .NET version 2.0

[Rob Boehne]

The fix was just to compute and prepend a PATH entry to find the .NET version 2 framework compiler, and I’m not sure how this might be turned into a patch for SCons.  Since it’s C# and not C/C++ it’s using the contributed C# builder, which isn’t a part of scons proper.  Also, the project is a closed-source SWIG wrapper to Adobe’s PDF Library, so I can’t share it.

From: Scons-users <scons-users-bounces at scons.org<mailto:scons-users-bounces at scons.org>> on behalf of Bill Deegan <bill at baddogconsulting.com<mailto:bill at baddogconsulting.com>>
Reply-To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Date: Friday, February 24, 2017 at 4:53 PM
To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Subject: Re: [Scons-users] How to build .NET version 2.0

Rob,

If you want to share the build via https://bitbucket.org/scons/scons-contrib. Please make a pull request.

Thanks,
Bill

On Fri, Feb 24, 2017 at 1:58 PM, Rob Boehne <robb at datalogics.com<mailto:robb at datalogics.com>> wrote:
Yes – but it always seems to set it to the 4.0 version, and I don’t see any way to change it.  Even in the old build, we modified the output of the environment vcvarsall.bat created to point to the 2.0 framework’s “csc.exe”.  I’ve got something working now, but with all the manual munging it’s going to need adjustments with newer versions of VS (I’m guessing).   However – it’s a lot less complicated than the previous version is, so it’s a big win either way.

Thanks,

Rob

From: Scons-users <scons-users-bounces at scons.org<mailto:scons-users-bounces at scons.org>> on behalf of Bill Deegan <bill at baddogconsulting.com<mailto:bill at baddogconsulting.com>>
Reply-To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Date: Friday, February 24, 2017 at 3:37 PM

To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Subject: Re: [Scons-users] How to build .NET version 2.0

Rob,

Doesn't vcvarsall.bat from 2013 set the path to pick csc.exe up?

-Bill

On Fri, Feb 24, 2017 at 12:27 PM, Rob Boehne <robb at datalogics.com<mailto:robb at datalogics.com>> wrote:
Bill,

The newest version I have installed is the one I’m using (2013 / 12.0) so specifically, I need to find the “csc.exe” in the appropriate versioned subdirectory of
c:\Windows\Microsoft.NET\Framework[64]

The docs say that I should have some of these variables set in the environment’s ‘MSVS’ entry, but the only things in it are
 { ‘SOLUTIONSUFFIX’: ‘.sln’,
 ‘PROJECTSUFFIX’: ‘.vcxproj’,}

So it looks like I have to set the version, and compute the correct path to “csc.exe” then prepend that entry myself.  Unless someone knows a better option?


From: Scons-users <scons-users-bounces at scons.org<mailto:scons-users-bounces at scons.org>> on behalf of Bill Deegan <bill at baddogconsulting.com<mailto:bill at baddogconsulting.com>>
Reply-To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Date: Friday, February 24, 2017 at 1:09 PM

To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Subject: Re: [Scons-users] How to build .NET version 2.0

Rob,

Would using:

MSVC_USE_SCRIPT to point at your specific vcvarsall.bat work?

(See manpage for details)


-Bill

On Fri, Feb 24, 2017 at 10:49 AM, Rob Boehne <robb at datalogics.com<mailto:robb at datalogics.com>> wrote:
Bill,

Yes, we have VS 2008, and 2013 sp5, but I think the .NET SDK might be packaged separately as well, under C:\Windows\Microsoft.NET\Framework[64]  I have v1.0, 1.1, 2.0, 3.0, 3.5 and 4.0.
The dll creation's environment is the only thing that’s different between the legacy build and the one with my the latest tools. - I.e. the commands are the same but the PATH isn’t specified and is different.

Rob

From: Scons-users <scons-users-bounces at scons.org<mailto:scons-users-bounces at scons.org>> on behalf of Bill Deegan <bill at baddogconsulting.com<mailto:bill at baddogconsulting.com>>
Reply-To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Date: Friday, February 24, 2017 at 12:15 PM
To: SCons users mailing list <scons-users at scons.org<mailto:scons-users at scons.org>>
Subject: Re: [Scons-users] How to build .NET version 2.0

Rob,

Do you have several MS VS's installed?
One with older and one with newer .net?

-Bill

On Fri, Feb 24, 2017 at 9:47 AM, Rob Boehne <robb at datalogics.com<mailto:robb at datalogics.com>> wrote:
All,

I’m updating to the latest scons-2.5.1 from a hacked v0.97, and my current problem with it is that it’s building .NET 4.0 when I want .NET 2.0.
The old version in my SConstruct had code that would run vcvarsall.bat for the target configuration, capture the environment and then manually set it in the builder environment.  It seems like a great deal of work (and more importantly, code) to get this accomplished.  Is there a simpler way to specify this rather than manually computing and setting the build environment’s [‘ENV’][‘PATH’] ?
I’m using the scons C# builders linked to in the wiki.

TIA,

Robert Boehne

_______________________________________________
Scons-users mailing list
Scons-users at scons.org<mailto:Scons-users at scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users



_______________________________________________
Scons-users mailing list
Scons-users at scons.org<mailto:Scons-users at scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users



_______________________________________________
Scons-users mailing list
Scons-users at scons.org<mailto:Scons-users at scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users



_______________________________________________
Scons-users mailing list
Scons-users at scons.org<mailto:Scons-users at scons.org>
https://pairlist4.pair.net/mailman/listinfo/scons-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20170227/38688792/attachment.html>