Recent changes to BuildProcess_VisualStudio

BuildProcess_VisualStudio modified by Dan Wagner

Dan Wagner — Mon, 29 Aug 2022 18:52:49 -0000

--- v30
+++ v31
@@ -1,6 +1,8 @@
 # FVS Home Repository Has Moved
 Please note, the official FVS repository has recently migrated from Source Forge to GitHub.  Please visit us at https://github.com/USDAForestService/ForestVegetationSimulator for the latest in code and wiki updates.  This Source Forge repository will no longer be maintained, and is kept here as archival reference only.  

+
+-----
 # The Build Process in Windows using Visual Studio
 _Don Robinson, [ESSA Technologies](http://www.essa.com), October 2021_

BuildProcess_VisualStudio modified by Dan Wagner

Dan Wagner — Mon, 29 Aug 2022 18:50:10 -0000

--- v29
+++ v30
@@ -1,3 +1,6 @@
+# FVS Home Repository Has Moved
+Please note, the official FVS repository has recently migrated from Source Forge to GitHub.  Please visit us at https://github.com/USDAForestService/ForestVegetationSimulator for the latest in code and wiki updates.  This Source Forge repository will no longer be maintained, and is kept here as archival reference only.  
+
 # The Build Process in Windows using Visual Studio
 _Don Robinson, [ESSA Technologies](http://www.essa.com), October 2021_

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:51:40 -0000

--- v28
+++ v29
@@ -98,11 +98,11 @@
 FVSsql           | No                          | C            | _**FVSsql.dll**_
 ZERO_CHECK       | Yes (optional)              | \-           | \-

-The Visual Studio Solution Explorer tree control shown below will let you see each project component. You can navigate around this tree control to locate source code of various kinds. The bulk of the FVS code will be in the FVS_bc project. When collapsed, it will look something like this:
+The Visual Studio Solution Explorer tree control shown below will let you see each project component. You can navigate around this tree control to locate source code of various kinds. The bulk of the FVS code will be in the FVS_bc project. When tided up and collapsed, it will look something like this:

 ![image vs2010 not loaded](https://sourceforge.net/p/open-fvs/wiki/BuildProcess_VisualStudio/attachment/VS2010.png)

-Before trying to compile the FVSbc variant you should right-click the **FVSbc** project and select **Set as StartUp Project**. It will then appear in bold font. Note that the FVSbc project is different from the FVS_bc project. The first of these builds the final executable; the second builds the DLL which contains most of the model code (and is linked to the executable, along with other DLL components). 
+Before trying to compile the FVSbc variant you should right-click the **FVSbc** project and select **Set as StartUp Project**. It will then appear in bold font (as shown above). Note that the FVSbc project is different from the FVS_bc project. The first of these builds the final executable; the second builds the DLL which contains most of the model code (and is linked to the executable, along with other DLL components). 

 **This feature of Cmake could use some improvement** The Cmake program does not automatically place the F77 include files in the proper sequence needed to compile correctly. To correct this, you will probably need to edit the order in which these files are accessed. To do this for the BC variant, right click on the FVS_bc component and select Properties > Fortran > General > Additional Include Directories. The select the Edit... option from the drop-down list and re-order the include files as shown below. The moved block of line is shown in bold face:

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:49:32 -0000

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:45:54 -0000

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:45:08 -0000

--- v25
+++ v26
@@ -100,7 +100,7 @@

 The Visual Studio Solution Explorer tree control shown below will let you see each project component. You can navigate around this tree control to locate source code of various kinds. The bulk of the FVS code will be in the FVS_bc project. When collapsed, it will look something like this:

-![image vs2010a not loaded](https://sourceforge.net/p/open-fvs/wiki/BuildProcess_VisualStudio/attachment/VS2010.png)
+![image vs2010 not loaded](https://sourceforge.net/p/open-fvs/wiki/BuildProcess_VisualStudio/attachment/VS2010.png)

 Before trying to compile the FVSbc variant you should right-click the **FVSbc** project and select **Set as StartUp Project**. It will then appear in bold font. Note that the FVSbc project is different from the FVS_bc project. The first of these builds the final executable; the second builds the DLL which contains most of the model code (and is linked to the executable, along with other DLL components).

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:44:15 -0000

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:37:36 -0000

--- v23
+++ v24
@@ -18,7 +18,7 @@
 ## Getting the Necessary Tools
 You will need Administrator privileges to install the necessary tools, so ensure you have that before proceeding.

-Building with Visual Studio requires **Microsoft Visual Studio 2010** and the **Intel Fortran XE 2011 compiler**. More recent versions of Visual Studio (including free or lower cost "Express" and free "Community" versions), and other compliant compilers (such as earlier versions of Visual Studio) _may work_, but have not been tested. Information about VS2010 is found at [www.microsoft.com](http://www.microsoft.com/visualstudio/eng/downloads). Information about the Intel compiler is found at [http://software.intel.com](http://software.intel.com/en-us/intel-visual-fortran-composer-xe-evaluation). You must have these both installed before continuing. Explaining the use of VS2010 is beyond the scope of this wiki page. 
+Building with Visual Studio requires **Microsoft Visual Studio 2010** and the **Intel Fortran XE 2011 compiler**. The instructions found on this page are known to work for these two releases. More recent versions of Visual Studio (including free or lower cost "Express" and free "Community" versions), and other compliant compilers _may work_, but have not been tested. Information about Visual Studio is found at [www.visualstudio.microsoft.com](https://visualstudio.microsoft.com/downloads/). Information about the Intel compiler is found at [http://software.intel.com](http://software.intel.com/en-us/intel-visual-fortran-composer-xe-evaluation). You must have these both installed before continuing. 

 You will also need to install the **Cmake** system, which can be found at [http://cmake.org](http://cmake.org/cmake/resources/software.html). The Cmake build steps described below have been tested with _Version 2.8_, which is now quite old. This older version can be downloaded [here](https://github.com/Kitware/CMake/releases/download/v2.8.12.2/cmake-2.8.1). During the installation process for Windows, you will need to select the option "Add CMake to the system PATH..." for all users or current user. If you get an error during the installation saying that the PATH is too long and cannot be edited, you will need to edit it manually to include the folder where Cmake is installed.

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:33:17 -0000

--- v22
+++ v23
@@ -20,7 +20,7 @@

 Building with Visual Studio requires **Microsoft Visual Studio 2010** and the **Intel Fortran XE 2011 compiler**. More recent versions of Visual Studio (including free or lower cost "Express" and free "Community" versions), and other compliant compilers (such as earlier versions of Visual Studio) _may work_, but have not been tested. Information about VS2010 is found at [www.microsoft.com](http://www.microsoft.com/visualstudio/eng/downloads). Information about the Intel compiler is found at [http://software.intel.com](http://software.intel.com/en-us/intel-visual-fortran-composer-xe-evaluation). You must have these both installed before continuing. Explaining the use of VS2010 is beyond the scope of this wiki page. 

-You will also need to install the **Cmake** system, which can be found at [http://cmake.org](http://cmake.org/cmake/resources/software.html). Download and install the latest version from the "Binary distributions" table. During the installation process for Windows, you will need to select the option "Add CMake to the system PATH..." for all users or current user. If you get an error during the installation saying that the PATH is too long and cannot be edited, you will need to edit it manually to include the folder where Cmake is installed. The Cmake build steps described below have been tested with _Version 2.8_. 
+You will also need to install the **Cmake** system, which can be found at [http://cmake.org](http://cmake.org/cmake/resources/software.html). The Cmake build steps described below have been tested with _Version 2.8_, which is now quite old. This older version can be downloaded [here](https://github.com/Kitware/CMake/releases/download/v2.8.12.2/cmake-2.8.1). During the installation process for Windows, you will need to select the option "Add CMake to the system PATH..." for all users or current user. If you get an error during the installation saying that the PATH is too long and cannot be edited, you will need to edit it manually to include the folder where Cmake is installed.

 Your development work will likely mean that you will eventually merge your work into the trunk code. Please see the [Testing](Testing) wiki to learn about the requirements for testing model behavior prior to integrating code. Note that creating and running FVS tests requires the following (Unix) utilities: `make, echo, grep, diff` and `rm`.

BuildProcess_VisualStudio modified by Donald Robinson

Donald Robinson — Tue, 12 Oct 2021 23:25:18 -0000

--- v21
+++ v22
@@ -1,5 +1,5 @@
 # The Build Process in Windows using Visual Studio
-_Don Robinson, [ESSA Technologies](http://www.essa.com), August 2021_
+_Don Robinson, [ESSA Technologies](http://www.essa.com), October 2021_

 This wiki documents the process of setting things up on a Windows PC so you can build FVS executables from the source files in the open-fvs repository. Builds of 32-bit  and 64-bit builds have been tested on Windows 7-10. For more information on the build process, including information for builds on other platforms please refer to [BuildProcess_UnixAlike](BuildProcess_UnixAlike), [BuildProcess_MinGW](BuildProcess_MinGW) or the [FAQ](FAQ). 

@@ -94,7 +94,7 @@
 All_BUILD        | Yes (optional)              | \-           | \- 
 FVS_bc          | No                          | FORTRAN      | **_FVS_bc.dll_**
 FVSbc           | No                          | FORTRAN      | **_FVSbc.exe_**
-FVSfofem         | No                          | C            | **_FVSfofem.dll_**
+FVSfofem         | No                          | C/C++            | **_FVSfofem.dll_**
 FVSsql           | No                          | C            | _**FVSsql.dll**_
 ZERO_CHECK       | Yes (optional)              | \-           | \- 

@@ -113,7 +113,7 @@
     C:\open-fvs\trunk\bin\FVSbc_CmakeDir\..\..\common
     C:\open-fvs\trunk\bin\FVSbc_CmakeDir\..\..\common\$(ConfigurationName)**

-When you start Visual Studio, the first build of the variant should include all projects, but subsequent builds do not need to repeatedly perform the same internal checks. An example of a component that can be excluded after the first build is ZERO_CHECK. This  component only needs to be created once. In Visual Studio such non-essential projects can be unloaded by right-clicking the project and selecting **Unload Project** after the first successful build.  The image shown above shows these to run-once sub-projects as unloaded.
+When you start Visual Studio, the first build of the variant should include all projects, but subsequent builds do not need to repeatedly perform the same internal checks. An example of a component that can be excluded after the first build is ZERO_CHECK. This  component only needs to be created once. In Visual Studio such non-essential projects can be unloaded by right-clicking the project and selecting **Unload Project** after the first successful build.  The image shown above shows these to run-once sub-projects as unloaded. After unloading, you can also remove the unloaded projects if you wish.

 It is often helpful to further automate the coding and debugging process by providing a response file that reproduces the file names entered by typing at the command line, making it unnecessary to repeatedly type input and output file names. This is easy to do by creating a response file using any valid file name (e.g. 'qbc01.rsp'). Then right-click the FVSbc project in the Solution Explorer tree and select **Properties**. From the tree-control highlight **Debugging** and modify the Command Arguments to provide input redirection.