Revision: 76470
          http://sourceforge.net/p/brlcad/code/76470
Author:   starseeker
Date:     2020-07-24 19:51:31 +0000 (Fri, 24 Jul 2020)
Log Message:
-----------
Reorganize, note how to specify SDK

Modified Paths:
--------------
    brlcad/trunk/doc/README.Windows

Modified: brlcad/trunk/doc/README.Windows
===================================================================
--- brlcad/trunk/doc/README.Windows     2020-07-24 15:59:27 UTC (rev 76469)
+++ brlcad/trunk/doc/README.Windows     2020-07-24 19:51:31 UTC (rev 76470)
@@ -14,46 +14,7 @@
 Visual Studio
 -------------
 
-=== Notes on Windows 10 with latest SDK ===
-Because Tk before 8.6.8 cannot be built with the latest Windows SDK
-(naming conflicts; see [1]), an earlier one (10.0.15063.0 is the
-last working version) is needed (available at [2]).
 
-Targets `tk`, `tkstub` and `libfb` need to be changed to use this SDK
-(right click on a target -> Configuration Properties -> General;
-select the SDK in Windows SDK Version).
-
-Compilation is then unchanged from the below.
-
-[1]: https://core.tcl.tk/tk/tktview?name=3d34589aa0
-[2]: https://developer.microsoft.com/en-us/windows/downloads/sdk-archive
-
-===========================================
-
-=== Notes on Visual Studio 14 2015 ===
-
-In order to build this version (required to build the Creo 3 converter)
-with CMake, you must ensure that Microsoft's "rc.exe" program is
-installed and findable by CMake.
-
-To install "rc.exe", run or re-run the Visual Studio installer and enable
-Visual C++ components and "Visual Studio Extensibility Tools Update 1" under
-the "Common Tools" section.
-
-The extensibility tools can become unselected by default in some
-configurations. Verify "rc.exe" is installed in:
-
-"C:\Program Files (x86)\Windows Kits\8.1\bin\x64"
-
-Add that directory to your "Path" user variable so CMake will be able to
-locate the rc executable.
-
-See:
-https://stackoverflow.com/questions/43847542/rc-exe-no-longer-found-in-vs-2015-command-prompt
-
-======================================
-
-
 To build with CMake and Visual Studio, the first step is to obtain the
 BRL-CAD sources and create a build directory.  In principle, it is not
 *required* to have a separate build directory, but with Windows and
@@ -93,6 +54,45 @@
 named PACKAGE and run it.  The end result should be an .exe file
 capable of installing BRL-CAD.
 
+===========================================
+
+=== Setting a specific SDK version ===
+
+If a particular version of the Windows SDK is needed, it is specified
+with CMAKE_SYSTEM_VERSION (for example, to use 10.0.15063.0 the user
+would define a New Entry in the CMake GUI before running configure,
+make the variable CMAKE_SYSTEM_VERSION as a string type, and assign the
+value of 10.0.15063.0.)
+
+Note that for this to work the SDK version in question must be
+installed on the system.
+
+===========================================
+
+=== Notes on Visual Studio 14 2015 ===
+
+In order to build this version (required to build the Creo 3 converter)
+with CMake, you must ensure that Microsoft's "rc.exe" program is
+installed and findable by CMake.
+
+To install "rc.exe", run or re-run the Visual Studio installer and enable
+Visual C++ components and "Visual Studio Extensibility Tools Update 1" under
+the "Common Tools" section.
+
+The extensibility tools can become unselected by default in some
+configurations. Verify "rc.exe" is installed in:
+
+"C:\Program Files (x86)\Windows Kits\8.1\bin\x64"
+
+Add that directory to your "Path" user variable so CMake will be able to
+locate the rc executable.
+
+See:
+https://stackoverflow.com/questions/43847542/rc-exe-no-longer-found-in-vs-2015-command-prompt
+
+======================================
+
+
 MINGW (WORK IN PROGRESS - THIS DOES NOT YET WORK!!!)
 -----
 

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.



_______________________________________________
BRL-CAD Source Commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-commits

Reply via email to