First misstep to report - selecting "typical" install type for Visual Studio Express (a logical choice for a newbie) results in NO C++ support! You need to choose "Custom" and then select C++ from the listed choices. According to the blog post I read, this was done to reduce the huge extra downloads required for C++ for those who will only use VB or C#. Lots of negative comments posted as a result of this change made about a year ago. So now I need to "redo" the install or create a C++ "project" in Visual Studio which will fail but offer to install the C++ support. Sigh!
Background: I looked at the VCVarsAll.bat to see what it was going to do and then did a Google search on it. After wading through lots of entries about Python not finding the .bat file, I found this link: https://msdn.microsoft.com/en-us/library/x4d2c09s.aspx which led me to this link: https://msdn.microsoft.com/en-us/library/f2ccy3wt.aspx So, based on that info, I surmised that command line access to the build tools is not installed by default as MS expects users to build using the IDE (It is named VISUAL Studio after all). I also found the "shortcuts" to opening a developer window with all the environment variables set in my Start menu. So one has two choices: 1) use the shortcut and then CD to where you want to do the NMAKE or 2) type the very long path name to the VCVarsAll.bat in the directory where you will do the NMAKE. In either case, the environment variables are NOT set permanently and are only good while the command prompt window remains open. I'll probably write a .bat file to run the VCVarsAll.bat and put it in the folder where I'll do the NMAKE to make that easier. I tried both approaches, neither of which worked (because the C++ tools aren't there). It took lots of digging to determine the cause and then to find the blog entry with the explanation. So I think I know what to do next but I'm not looking forward to another LONG download/install and will do that when I have the time to watch the grass grow! Gil B. On 9/13/2016 2:34 PM, Gil Barmwater wrote: > Chip, I will try to get a list of steps that works as well as missteps I > make along the way. E.g. I don't know if the Community version of > Visual Studio would work but I may try it on my desktop system once I > get the laptop with the Express version running. So far, I have found > the VCVarsAll.bat that Rick mentioned but haven't run it yet. > > For those "old hands" that do this stuff all the time, please excuse the > "noise" on this list :-). I'll try to keep the postings short and sweet. > > Gil B. > > On 9/13/2016 1:31 PM, Chip Davis wrote: >> Gil, please document your steps so the rest of us superannuated >> canines can follow your lead. >> >> -Chip- >> >> On 9/13/2016 9:18 AM, Rick McGuire wrote: >>> Gil, the C++ package has a batch file that will set a bunch of >>> environment variables and also add the needed directories to your >>> path. With the version I'm using, this is called VCVarsAll.bat. I'm >>> not sure what the bat file is named for the express version, but it >>> probably starts with VCVars. This batch file is also how you can >>> specify whether you wish to build your code as 32-bit or 64-bit. >>> >>> Rick >>> >>> On Tue, Sep 13, 2016 at 9:10 AM, Gil Barmwater >>> <gbarmwa...@alum.rpi.edu <mailto:gbarmwa...@alum.rpi.edu>> wrote: >>> >>> The recent RexxLA Symposium inspired me to start looking at >>> writing and >>> building external routines and methods in C++ and, eventually, >>> building >>> the ooRexx project from a checked-out copy on Source Forge. I decided >>> to start with the excellent presentation from last year's Symposium by >>> Rony so I downloaded his presentation, code and makefiles and reviewed >>> them enough to feel like I could attempt to get them to work. But I >>> needed a C++ package so, at Rene's suggestion at this year's >>> Symposium, >>> I downloaded and installed Visual Studio Express (I chose not to >>> install >>> Community even though that was the link that Rene supplied). This >>> is a >>> huge package - 12GB - that took a long time to install but it >>> eventually >>> completed. >>> >>> Now I'm confused as to what to do next! Do I need to do anything in >>> Visual Studio to get the C++ tools - like NMAKE - installed? Typing >>> nmake (or cl even) at a command prompt gives me "'nmake' is not >>> recognized as an internal or external command, operable program or >>> batch >>> file." So clearly, the C++ tools are not in my path. >>> >>> Any help for this old dog trying to learn new tricks is greatly >>> appreciated! >>> >>> -- >>> >>> Gil Barmwater >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> -- Gil Barmwater ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
