Revision: 75976
          http://sourceforge.net/p/brlcad/code/75976
Author:   starseeker
Date:     2020-05-28 21:46:40 +0000 (Thu, 28 May 2020)
Log Message:
-----------
Put the three most common platforms at the top level

Modified Paths:
--------------
    brlcad/trunk/doc/CMakeLists.txt

Added Paths:
-----------
    brlcad/trunk/doc/README.Linux
    brlcad/trunk/doc/README.MacOSX
    brlcad/trunk/doc/README.Windows
    brlcad/trunk/doc/README.other/

Removed Paths:
-------------
    brlcad/trunk/doc/README/
    brlcad/trunk/doc/README.other/README.Linux
    brlcad/trunk/doc/README.other/README.MacOSX
    brlcad/trunk/doc/README.other/README.Windows

Modified: brlcad/trunk/doc/CMakeLists.txt
===================================================================
--- brlcad/trunk/doc/CMakeLists.txt     2020-05-28 21:33:48 UTC (rev 75975)
+++ brlcad/trunk/doc/CMakeLists.txt     2020-05-28 21:46:40 UTC (rev 75976)
@@ -6,14 +6,14 @@
   BRL-CAD.bib
   IDEAS
   PROJECTS
-  README/README.AIX
-  README/README.BSD
-  README/README.IRIX
-  README/README.Linux
-  README/README.MacOSX
-  README/README.Solaris
-  README/README.VAX
-  README/README.Windows
+  README.Linux
+  README.MacOSX
+  README.Windows
+  README.other/README.AIX
+  README.other/README.BSD
+  README.other/README.IRIX
+  README.other/README.Solaris
+  README.other/README.VAX
   archer_ack.txt
   checklist.txt
   description.txt

Copied: brlcad/trunk/doc/README.Linux (from rev 75972, 
brlcad/trunk/doc/README/README.Linux)
===================================================================
--- brlcad/trunk/doc/README.Linux                               (rev 0)
+++ brlcad/trunk/doc/README.Linux       2020-05-28 21:46:40 UTC (rev 75976)
@@ -0,0 +1,128 @@
+BRL-CAD on Linux README
+=======================
+
+Below are installation and platform notes of relevance to particular
+Linux distributions.
+
+Table of Contents
+-----------------
+Parallel Builds
+64-bit Compile
+32-bit Compile
+Arch Linux
+Ubuntu/Debian
+PPC64 Linux
+
+Parallel Builds
+---------------
+BRL-CAD compilation can take advantage of multiple CPUs.  With
+Make based builds, this is done using the "-j" flag - e.g. a
+six core machine will build faster using "make -j6" to utilize
+all cores.
+
+
+64-bit Compile (on a platform that defaults to 32-bit)
+--------------
+
+cmake ../brlcad -DBRLCAD_WORD_SIZE=32BIT
+
+32-bit Compile (on a platform that defaults to 64-bit)
+--------------
+
+cmake ../brlcad -DBRLCAD_WORD_SIZE=64BIT
+
+* Note that in both of the above situations you need both a compiler that
+works in the alternate mode and system libraries of the correct type.
+
+
+Arch Linux
+----------
+
+An example PKGBUILD and needed scripts are provided in misc/archlinux.
+Review and edit the PKGBUILD to suit your preferred configuration and
+build situation (e.g. building from a tarball vs building from SVN).
+Run `makepkg` in that directory to build the package.
+
+
+Ubuntu/Debian
+-------------
+
+Users of Ubuntu, Debian, and other similar packaging distributions of
+Linux will need to ensure that a few essentials are in place before
+you will be able to compile BRL-CAD.
+
+Following the build instructions in the INSTALL file.  You will need:
+
+gcc (3+, e.g. 4.0.3)
+g++ (3+, e.g. 4.0.3)
+make (e.g. gnu make 3.8.0)
+cmake (2.8.8 or newer)
+
+All three of those have implicit dependencies on other packages.
+
+You will also want to make sure that you have the X11 development
+headers installed:
+
+  apt-get install xserver-xorg-dev libx11-dev libxi-dev libxext-dev
+
+Other development packages needed to build on Debian-based platforms:
+
+  for building the Tcl/Tk libraries:  libfontconfig-dev
+
+  for OpenGL: libglu1-mesa-dev
+
+Note there is a supported Debian package generation script in file
+'sh/make_deb.sh' which can function only on a Debian or Ubuntu system.
+It can be used like so:
+
+  $ cd <BRL-CAD source directory>
+
+  # get help for the script:
+  $ ./sh/make_deb.sh
+
+  # create a binary package:
+  $ ./sh/make_deb.sh -b
+
+You can customize the script's cmake build options by modifying the
+file 'misc/debian/rules'.  Note that the BRL-CAD source directory
+should be deleted and recreated for each new attempt at package
+generation.
+
+
+Redhat/Fedora
+-------------
+
+Development packages for building on Redhat/Fedora platforms:
+
+  yum install libX11-devel
+  yum install libXext-devel    # optional
+  yum install libXi-devel      # optional
+  yum install freetype-devel   # optional
+  yum install fontconfig-devel # optional
+  yum install mesa-libGL-devel # optional
+
+To determine what particular version of Redhat or Fedora you are
+using, check these files:
+
+cat /etc/redhat-release
+cat /etc/fedora-release
+
+Note there is a supported rpm package generation script in file
+'sh/make_rpm.sh' which can only function on a Fedora or openSUSE
+system.  It can be used like so:
+
+  $ cd <BRL-CAD source directory>
+
+  # create an rpm file:
+  $ ./sh/make_rpm.sh
+
+It is also possible to create an RPM package using CPack with the
+make package build target, on systems with the proper RPM tools.
+
+PPC64 Linux
+-----------
+
+If you happen to be installing on a ppc64 Linux system, the binaries
+may not resolve correctly without being installed first.  Be sure to
+install before testing applications (i.e., even before running the
+benchmark or "make test").

Copied: brlcad/trunk/doc/README.MacOSX (from rev 75972, 
brlcad/trunk/doc/README/README.MacOSX)
===================================================================
--- brlcad/trunk/doc/README.MacOSX                              (rev 0)
+++ brlcad/trunk/doc/README.MacOSX      2020-05-28 21:46:40 UTC (rev 75976)
@@ -0,0 +1,109 @@
+BRL-CAD on Max OS X README
+==========================
+
+Being that this is one of the newest architectures to be added and
+officially supported, there are some issues to keep in mind with the
+installation when building from the sources.  Beyond the notes
+provided here, building on Mac OS X can generally be considered the
+same as the UNIX, BSD, and Linux platforms.
+
+Table of Contents
+-----------------
+  Introduction
+  Table of Contents
+  CMake
+  X11 Window Server
+  Supported Versions
+  Mac OS X 10.2
+  Parallel Builds
+  Bugs
+
+CMake
+-----------------
+Kitware provides Mac OSX compilations of CMake:
+
+http://www.cmake.org/cmake/resources/software.html
+
+
+X11 Window Server
+-----------------
+You'll need to install an X11 server if you would like to build Tk and
+have a graphical user interface.  Apple's X11 is the recommended X
+Window Server, but XQuartz should work too and is often newer than the
+official Apple version:  http://xquartz.macosforge.org
+
+Supported Versions
+------------------
+BRL-CAD is generally only "extensively" tested by the developers on
+the latest released version of Mac OS X.  That is to say that
+although the BRL-CAD package should build on prior versions of the Mac
+OS X operating system, they are generally and eventually not
+maintained and will require additional effort to obtain a build.
+Compiling on 10.3 or 10.4 should complete successfully.  Due to a
+variety of significant application programming interface issues in
+early releases of Mac OS X, versions prior to 10.2 are unsupported.
+
+Parallel Builds
+---------------
+As many workstation and server systems shipped by Apple are
+multiprocessor systems, you can enjoy the benefits of decreased
+compile times by utilizing the "-j" option to make.  After running
+configure, run "make -j2" to build on a 2-processor system.
+
+Universal Builds
+----------------
+
+Universal builds have not been fully vetted due to how BRL-CAD
+serializes data to disk. BRL-CAD's CMake logic is not currently
+set up to support this type of build, but plans to in the future.
+
+CMake and Mac OSX
+-----------------
+
+On a default configuration, CMake has some problems performing parallel
+builds on OSX - typically this will manifest itself as a series of
+"too many open files" errors.  So far, the way to work around this in
+OSX 10.5 is to set the following system control variables to 50,000:
+
+kern.maxfiles
+kern.maxfilesperproc
+
+(check the current values using "sysctl <variable>" on the command line)
+
+and up the maxfiles limit in /etc/launchd.conf:
+
+limit maxfiles 50000 unlimited
+
+This is not widely tested, and OSX has quite a few limit settings that
+may or may not apply (and may change from one version to the next.)  As
+we get a better feel for various platforms we can assemble a table of
+required settings.  Other programs have this issue as well, so searching
+online may prove fruitful.
+
+So far, if parallel building doesn't work due to the above issue a
+non-parallel build will still succeed.  Another workaround is to build
+just subdirectories (e.g. src/other, doc, etc.) individually and then
+do a toplevel make in non-parallel mode to finalize the build.
+
+OpenSceneGraph and OSX
+----------------------
+For 32bit OSX builds of an X11+OpenSceneGraph BRL-CAD:
+cmake .. -DBRLCAD_BUNDLED_LIBS=BUNDLED -DBRLCAD_ENABLE_OSG=ON
+-DBRLCAD_REGEX=SYSTEM -DBRLCAD_WORD_SIZE=32BIT -DOSG_WINDOWING_SYSTEM=X11
+
+
+Tips
+----
+
+If you need to get information about your machine and OSX version, try
+these commands:
+
+sw_vers -productVersion
+uname -a
+
+Bugs
+----
+The only known bugs specific to Mac OS X are limitations of Tk or the
+X11 event handler that are generally outside of BRL-CAD's domain.
+Refer to BUGS for more general details on known bugs and reporting
+mechanisms.

Copied: brlcad/trunk/doc/README.Windows (from rev 75972, 
brlcad/trunk/doc/README/README.Windows)
===================================================================
--- brlcad/trunk/doc/README.Windows                             (rev 0)
+++ brlcad/trunk/doc/README.Windows     2020-05-28 21:46:40 UTC (rev 75976)
@@ -0,0 +1,113 @@
+BRL-CAD on Windows README
+=========================
+
+The usual way to build BRL-CAD for Windows is to use the CMake build
+system generator and the Microsoft Visual Studio C++ (MSVC) compiler.
+Recent versions of both (as of this writing, MSVC 2013 and CMake
+2.8.12+) are recommended.  If generating an installer, the Nullsoft
+Scriptable Install System (NSIS) tool is also required.
+
+In principle, BRL-CAD can be built using CMake and environments like
+Cygwin and/or Mingw/Msys, but the latter is largely untested and
+infrequently supported.  Enhancements or bug reports are welcome.
+
+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
+Visual Studio this is the only tested configuration.  Once those the
+sources are obtained and the build directory is created, run the CMake
+application and specify the source and build directories.
+
+Once CMake has the correct directory settings, select Configure.  If
+this is the first time running Configure with this build directory,
+CMake will prompt you to select a generator.  Look for your version of
+Visual Studio and select it.  Configuration should now proceed.
+
+It is normal for configuration to be a long process on Windows.  Once
+it is complete, you should see a list of red highlighted entries
+appear in the CMake interface.  Change any settings that appear to
+need changing and press Configure again.  The second pass should be
+shorter.  If no new red lines appear, the configuration is complete.
+
+The final CMake step, after completing Configuration, is to select
+Generate to create Visual Studio project files in the build directory.
+Once this is done, you may quit CMake.
+
+Navigate to your build directory.  You should see a BRLCAD solution
+file for Visual Studio.  Double-click that file, and Visual Studio
+should launch.  It will load the targets (a default configuration of
+BRL-CAD on Windows will generate over 800 of them) and a large list of
+targets will appear.  To build everything look for a target named
+ALL_BUILD.  Start compiling that target.
+
+Once compilation is successfully complete, you can find the compiled
+executables in a 'bin' directory in your build directory.  For
+example, mged.exe would be in brlcad-svn-trunk\.build\Debug\bin if
+brlcad-svn-trunk\.build is the build directory specified to CMake and
+CMAKE_BUILD_TYPE was set to Debug.
+
+You may want to produce an NSIS installer.  If so, locate a target
+named PACKAGE and run it.  The end result should be an .exe file
+capable of installing BRL-CAD.
+
+MINGW (WORK IN PROGRESS - THIS DOES NOT YET WORK!!!)
+-----
+
+After installing the MINGW system, set up as follows:
+
+set path=%path%;"C:\Program Files (x86)\CMake\bin"
+set path=%path%;C:\MinGW\bin
+
+now make a build directory, and run CMake:
+
+cmake ..\brlcad -G "MinGW Makefiles" -DBRLCAD_BUNDLED_LIBS=BUNDLED
+
+mingw32-make
+
+Note that you don't want to do this from an msys prompt that has
+sh in the path.  (ConEmu can make using the standard Windows command
+prompt a bit more tolerable:  http://conemu.github.io)
+

Deleted: brlcad/trunk/doc/README.other/README.Linux
===================================================================
--- brlcad/trunk/doc/README/README.Linux        2020-05-28 21:33:48 UTC (rev 
75975)
+++ brlcad/trunk/doc/README.other/README.Linux  2020-05-28 21:46:40 UTC (rev 
75976)
@@ -1,128 +0,0 @@
-BRL-CAD on Linux README
-=======================
-
-Below are installation and platform notes of relevance to particular
-Linux distributions.
-
-Table of Contents
------------------
-Parallel Builds
-64-bit Compile
-32-bit Compile
-Arch Linux
-Ubuntu/Debian
-PPC64 Linux
-
-Parallel Builds
----------------
-BRL-CAD compilation can take advantage of multiple CPUs.  With
-Make based builds, this is done using the "-j" flag - e.g. a
-six core machine will build faster using "make -j6" to utilize
-all cores.
-
-
-64-bit Compile (on a platform that defaults to 32-bit)
---------------
-
-cmake ../brlcad -DBRLCAD_WORD_SIZE=32BIT
-
-32-bit Compile (on a platform that defaults to 64-bit)
---------------
-
-cmake ../brlcad -DBRLCAD_WORD_SIZE=64BIT
-
-* Note that in both of the above situations you need both a compiler that
-works in the alternate mode and system libraries of the correct type.
-
-
-Arch Linux
-----------
-
-An example PKGBUILD and needed scripts are provided in misc/archlinux.
-Review and edit the PKGBUILD to suit your preferred configuration and
-build situation (e.g. building from a tarball vs building from SVN).
-Run `makepkg` in that directory to build the package.
-
-
-Ubuntu/Debian
--------------
-
-Users of Ubuntu, Debian, and other similar packaging distributions of
-Linux will need to ensure that a few essentials are in place before
-you will be able to compile BRL-CAD.
-
-Following the build instructions in the INSTALL file.  You will need:
-
-gcc (3+, e.g. 4.0.3)
-g++ (3+, e.g. 4.0.3)
-make (e.g. gnu make 3.8.0)
-cmake (2.8.8 or newer)
-
-All three of those have implicit dependencies on other packages.
-
-You will also want to make sure that you have the X11 development
-headers installed:
-
-  apt-get install xserver-xorg-dev libx11-dev libxi-dev libxext-dev
-
-Other development packages needed to build on Debian-based platforms:
-
-  for building the Tcl/Tk libraries:  libfontconfig-dev
-
-  for OpenGL: libglu1-mesa-dev
-
-Note there is a supported Debian package generation script in file
-'sh/make_deb.sh' which can function only on a Debian or Ubuntu system.
-It can be used like so:
-
-  $ cd <BRL-CAD source directory>
-
-  # get help for the script:
-  $ ./sh/make_deb.sh
-
-  # create a binary package:
-  $ ./sh/make_deb.sh -b
-
-You can customize the script's cmake build options by modifying the
-file 'misc/debian/rules'.  Note that the BRL-CAD source directory
-should be deleted and recreated for each new attempt at package
-generation.
-
-
-Redhat/Fedora
--------------
-
-Development packages for building on Redhat/Fedora platforms:
-
-  yum install libX11-devel
-  yum install libXext-devel    # optional
-  yum install libXi-devel      # optional
-  yum install freetype-devel   # optional
-  yum install fontconfig-devel # optional
-  yum install mesa-libGL-devel # optional
-
-To determine what particular version of Redhat or Fedora you are
-using, check these files:
-
-cat /etc/redhat-release
-cat /etc/fedora-release
-
-Note there is a supported rpm package generation script in file
-'sh/make_rpm.sh' which can only function on a Fedora or openSUSE
-system.  It can be used like so:
-
-  $ cd <BRL-CAD source directory>
-
-  # create an rpm file:
-  $ ./sh/make_rpm.sh
-
-It is also possible to create an RPM package using CPack with the
-make package build target, on systems with the proper RPM tools.
-
-PPC64 Linux
------------
-
-If you happen to be installing on a ppc64 Linux system, the binaries
-may not resolve correctly without being installed first.  Be sure to
-install before testing applications (i.e., even before running the
-benchmark or "make test").

Deleted: brlcad/trunk/doc/README.other/README.MacOSX
===================================================================
--- brlcad/trunk/doc/README/README.MacOSX       2020-05-28 21:33:48 UTC (rev 
75975)
+++ brlcad/trunk/doc/README.other/README.MacOSX 2020-05-28 21:46:40 UTC (rev 
75976)
@@ -1,109 +0,0 @@
-BRL-CAD on Max OS X README
-==========================
-
-Being that this is one of the newest architectures to be added and
-officially supported, there are some issues to keep in mind with the
-installation when building from the sources.  Beyond the notes
-provided here, building on Mac OS X can generally be considered the
-same as the UNIX, BSD, and Linux platforms.
-
-Table of Contents
------------------
-  Introduction
-  Table of Contents
-  CMake
-  X11 Window Server
-  Supported Versions
-  Mac OS X 10.2
-  Parallel Builds
-  Bugs
-
-CMake
------------------
-Kitware provides Mac OSX compilations of CMake:
-
-http://www.cmake.org/cmake/resources/software.html
-
-
-X11 Window Server
------------------
-You'll need to install an X11 server if you would like to build Tk and
-have a graphical user interface.  Apple's X11 is the recommended X
-Window Server, but XQuartz should work too and is often newer than the
-official Apple version:  http://xquartz.macosforge.org
-
-Supported Versions
-------------------
-BRL-CAD is generally only "extensively" tested by the developers on
-the latest released version of Mac OS X.  That is to say that
-although the BRL-CAD package should build on prior versions of the Mac
-OS X operating system, they are generally and eventually not
-maintained and will require additional effort to obtain a build.
-Compiling on 10.3 or 10.4 should complete successfully.  Due to a
-variety of significant application programming interface issues in
-early releases of Mac OS X, versions prior to 10.2 are unsupported.
-
-Parallel Builds
----------------
-As many workstation and server systems shipped by Apple are
-multiprocessor systems, you can enjoy the benefits of decreased
-compile times by utilizing the "-j" option to make.  After running
-configure, run "make -j2" to build on a 2-processor system.
-
-Universal Builds
-----------------
-
-Universal builds have not been fully vetted due to how BRL-CAD
-serializes data to disk. BRL-CAD's CMake logic is not currently
-set up to support this type of build, but plans to in the future.
-
-CMake and Mac OSX
------------------
-
-On a default configuration, CMake has some problems performing parallel
-builds on OSX - typically this will manifest itself as a series of
-"too many open files" errors.  So far, the way to work around this in
-OSX 10.5 is to set the following system control variables to 50,000:
-
-kern.maxfiles
-kern.maxfilesperproc
-
-(check the current values using "sysctl <variable>" on the command line)
-
-and up the maxfiles limit in /etc/launchd.conf:
-
-limit maxfiles 50000 unlimited
-
-This is not widely tested, and OSX has quite a few limit settings that
-may or may not apply (and may change from one version to the next.)  As
-we get a better feel for various platforms we can assemble a table of
-required settings.  Other programs have this issue as well, so searching
-online may prove fruitful.
-
-So far, if parallel building doesn't work due to the above issue a
-non-parallel build will still succeed.  Another workaround is to build
-just subdirectories (e.g. src/other, doc, etc.) individually and then
-do a toplevel make in non-parallel mode to finalize the build.
-
-OpenSceneGraph and OSX
-----------------------
-For 32bit OSX builds of an X11+OpenSceneGraph BRL-CAD:
-cmake .. -DBRLCAD_BUNDLED_LIBS=BUNDLED -DBRLCAD_ENABLE_OSG=ON
--DBRLCAD_REGEX=SYSTEM -DBRLCAD_WORD_SIZE=32BIT -DOSG_WINDOWING_SYSTEM=X11
-
-
-Tips
-----
-
-If you need to get information about your machine and OSX version, try
-these commands:
-
-sw_vers -productVersion
-uname -a
-
-Bugs
-----
-The only known bugs specific to Mac OS X are limitations of Tk or the
-X11 event handler that are generally outside of BRL-CAD's domain.
-Refer to BUGS for more general details on known bugs and reporting
-mechanisms.

Deleted: brlcad/trunk/doc/README.other/README.Windows
===================================================================
--- brlcad/trunk/doc/README/README.Windows      2020-05-28 21:33:48 UTC (rev 
75975)
+++ brlcad/trunk/doc/README.other/README.Windows        2020-05-28 21:46:40 UTC 
(rev 75976)
@@ -1,113 +0,0 @@
-BRL-CAD on Windows README
-=========================
-
-The usual way to build BRL-CAD for Windows is to use the CMake build
-system generator and the Microsoft Visual Studio C++ (MSVC) compiler.
-Recent versions of both (as of this writing, MSVC 2013 and CMake
-2.8.12+) are recommended.  If generating an installer, the Nullsoft
-Scriptable Install System (NSIS) tool is also required.
-
-In principle, BRL-CAD can be built using CMake and environments like
-Cygwin and/or Mingw/Msys, but the latter is largely untested and
-infrequently supported.  Enhancements or bug reports are welcome.
-
-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
-Visual Studio this is the only tested configuration.  Once those the
-sources are obtained and the build directory is created, run the CMake
-application and specify the source and build directories.
-
-Once CMake has the correct directory settings, select Configure.  If
-this is the first time running Configure with this build directory,
-CMake will prompt you to select a generator.  Look for your version of
-Visual Studio and select it.  Configuration should now proceed.
-
-It is normal for configuration to be a long process on Windows.  Once
-it is complete, you should see a list of red highlighted entries
-appear in the CMake interface.  Change any settings that appear to
-need changing and press Configure again.  The second pass should be
-shorter.  If no new red lines appear, the configuration is complete.
-
-The final CMake step, after completing Configuration, is to select
-Generate to create Visual Studio project files in the build directory.
-Once this is done, you may quit CMake.
-
-Navigate to your build directory.  You should see a BRLCAD solution
-file for Visual Studio.  Double-click that file, and Visual Studio
-should launch.  It will load the targets (a default configuration of
-BRL-CAD on Windows will generate over 800 of them) and a large list of
-targets will appear.  To build everything look for a target named
-ALL_BUILD.  Start compiling that target.
-
-Once compilation is successfully complete, you can find the compiled
-executables in a 'bin' directory in your build directory.  For
-example, mged.exe would be in brlcad-svn-trunk\.build\Debug\bin if
-brlcad-svn-trunk\.build is the build directory specified to CMake and
-CMAKE_BUILD_TYPE was set to Debug.
-
-You may want to produce an NSIS installer.  If so, locate a target
-named PACKAGE and run it.  The end result should be an .exe file
-capable of installing BRL-CAD.
-
-MINGW (WORK IN PROGRESS - THIS DOES NOT YET WORK!!!)
------
-
-After installing the MINGW system, set up as follows:
-
-set path=%path%;"C:\Program Files (x86)\CMake\bin"
-set path=%path%;C:\MinGW\bin
-
-now make a build directory, and run CMake:
-
-cmake ..\brlcad -G "MinGW Makefiles" -DBRLCAD_BUNDLED_LIBS=BUNDLED
-
-mingw32-make
-
-Note that you don't want to do this from an msys prompt that has
-sh in the path.  (ConEmu can make using the standard Windows command
-prompt a bit more tolerable:  http://conemu.github.io)
-

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