Recent changes to BuildProcess_UnixAlike

BuildProcess_UnixAlike modified by Dan Wagner

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

--- v9
+++ v10
@@ -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 Unix

 _Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2019_

BuildProcess_UnixAlike modified by Dan Wagner

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

--- v8
+++ v9
@@ -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 Unix

 _Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2019_

BuildProcess_UnixAlike modified by Donald Robinson

Donald Robinson — Thu, 25 Jul 2019 21:27:24 -0000

--- v7
+++ v8
@@ -2,7 +2,7 @@

 _Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2019_

-This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ).  As an alternative to the **Cmake** build environment described below, you might also want to read this page  [BuildProcess_Rtools](BuildProcess_Rtools)] to see if the **make** tools are suitable.
+This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ).  As an alternative to the **Cmake** build environment described below, you might also want to read this page  [BuildProcess_Rtools](BuildProcess_Rtools) to see if the **make** tools are suitable.

 # Contents

BuildProcess_UnixAlike modified by Donald Robinson

Donald Robinson — Thu, 25 Jul 2019 21:26:39 -0000

--- v6
+++ v7
@@ -1,8 +1,8 @@
 # The Build Process in Unix

-_Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2015_
+_Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2019_

-This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ). 
+This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ).  As an alternative to the **Cmake** build environment described below, you might also want to read this page  [BuildProcess_Rtools](BuildProcess_Rtools)] to see if the **make** tools are suitable.

 # Contents

BuildProcess_UnixAlike modified by Donald Robinson

Donald Robinson — Tue, 23 Jul 2019 18:49:57 -0000

--- v5
+++ v6
@@ -50,7 +50,7 @@

     /MyFvsFiles/trunk/bin/FVSie_CmakeDir

-FVS variant subdirectories are named with the pattern `FVS**_CmakeDir`, where `***` is a 2-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States). 
+FVS variant subdirectories are named with the pattern `FVS**_CmakeDir`, where `**` is a 2-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States). 

 Cmake utilizes two kinds of files to create to create each variant makefile. First, it uses a master script file called **CMakeLists.txt** to control the creation of the makefile. (You are welcome to inspect this file, but editing it is not recommended for beginners.) This master script file utilizes a set of about 20 files in turn - one for each variant - with names like 'FVSie_sourceList.txt'. These files need to exist in the `trunk/bin` directory in order to build the variants.

BuildProcess_UnixAlike modified by Mike Shettles

Mike Shettles — Fri, 26 Apr 2019 16:00:05 -0000

--- v4
+++ v5
@@ -50,7 +50,7 @@

     /MyFvsFiles/trunk/bin/FVSie_CmakeDir

-FVS variant subdirectories are named with the pattern `FVS***_CmakeDir`, where `***` is a 2-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States). 
+FVS variant subdirectories are named with the pattern `FVS**_CmakeDir`, where `***` is a 2-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States). 

 Cmake utilizes two kinds of files to create to create each variant makefile. First, it uses a master script file called **CMakeLists.txt** to control the creation of the makefile. (You are welcome to inspect this file, but editing it is not recommended for beginners.) This master script file utilizes a set of about 20 files in turn - one for each variant - with names like 'FVSie_sourceList.txt'. These files need to exist in the `trunk/bin` directory in order to build the variants.

BuildProcess_UnixAlike modified by Mike Shettles

Mike Shettles — Fri, 26 Apr 2019 15:58:43 -0000

--- v3
+++ v4
@@ -48,15 +48,15 @@

 This will begin the creation of Unix makefiles for _all_ FVS variants. Each variant's Makefile will be placed in a sub-directory like this 

-    /MyFvsFiles/trunk/bin/FVSiec_CmakeDir
+    /MyFvsFiles/trunk/bin/FVSie_CmakeDir

-FVS variant subdirectories are named with the pattern `FVS***_CmakeDir`, where `***` is a 2- or 3-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States) optionally followed by a 1-letter abbreviation for an extension (e.g., `x` for the insect and disease extensions, or `c` for the climate extension). 
+FVS variant subdirectories are named with the pattern `FVS***_CmakeDir`, where `***` is a 2-letter abbreviation for the variant (e.g., 2-letters `ie` for Inland Empire or `ls` for Lake States). 

-Cmake utilizes two kinds of files to create to create each variant makefile. First, it uses a master script file called **CMakeLists.txt** to control the creation of the makefile. (You are welcome to inspect this file, but editing it is not recommended for beginners.) This master script file utilizes a set of about 20 files in turn - one for each variant - with names like 'FVSiec_sourceList.txt'. These files need to exist in the `trunk/bin` directory in order to build the variants. 
+Cmake utilizes two kinds of files to create to create each variant makefile. First, it uses a master script file called **CMakeLists.txt** to control the creation of the makefile. (You are welcome to inspect this file, but editing it is not recommended for beginners.) This master script file utilizes a set of about 20 files in turn - one for each variant - with names like 'FVSie_sourceList.txt'. These files need to exist in the `trunk/bin` directory in order to build the variants. 

 As Cmake creates each variant makefile you will see something like this: 

-    -- tobuild = <...>/trunk/bin/FVSiec_sourceList.txt
+    -- tobuild = <...>/trunk/bin/FVSie_sourceList.txt
     -- Building FVS variant with Unix
     -- The C compiler identification is GNU
     -- The Fortran compiler identification is GNU
@@ -70,11 +70,11 @@
     -- Detecting Fortran compiler ABI info - done
     -- Checking whether /usr/bin/gfortran supports Fortran 90
     -- Checking whether /usr/bin/gfortran supports Fortran 90 -- yes
-    -- slfn = FVSiec_sourceList.txt prgName= FVSiec
-    -- FVSvariant = FVSiec
+    -- slfn = FVSie_sourceList.txt prgName= FVSiec
+    -- FVSvariant = FVSie
     -- Configuring done
     -- Generating done
-    -- Build files have been written to: <...>/trunk/bin/FVSiec_CmakeDir
+    -- Build files have been written to: <...>/trunk/bin/FVSie_CmakeDir
     -- Configuring done
     -- Generating done
     -- Build files have been written to: <...>/trunk/bin
@@ -83,9 +83,9 @@

 ## Building the Executable for Development & Debugging

-At the command-line, `cd` to the directory containing the variant you wish to work with. In the example that follows the Inland Empire + Climate variant (iec) is used, and the makefile will be located here: 
+At the command-line, `cd` to the directory containing the variant you wish to work with. In the example that follows the Inland Empire variant (ie) is used, and the makefile will be located here: 

-    /MyFvsFiles/trunk/bin/FVSiec_CmakeDir/Makefile
+    /MyFvsFiles/trunk/bin/FVSie_CmakeDir/Makefile

 At the command-line, type this to begin building the executable: 

@@ -95,9 +95,9 @@

 **Component Name**   | **Language**
 ---------------------|--------------
-**_FVSiec_**         | FORTRAN 
+**_FVSie_**         | FORTRAN 
 **_libFVSfofem.so_** | C 
-**_libFVS_iec.so_**  | FORTRAN 
+**_libFVS_ie.so_**  | FORTRAN 
 **_libFVSsql.so_**   | C 

 Note: When Mac OS X is used as the build environment, the `.so` suffix will be replaced with a `.dylib` suffix.

BuildProcess_UnixAlike modified by Donald Robinson

Donald Robinson — Mon, 13 Jul 2015 20:48:18 -0000

--- v2
+++ v3
@@ -1,6 +1,6 @@
 # The Build Process in Unix

-_Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2014_
+_Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2015_

 This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ).

BuildProcess_UnixAlike modified by Donald Robinson

Donald Robinson — Mon, 13 Jul 2015 20:47:49 -0000

--- v1
+++ v2
@@ -1,6 +1,6 @@
 # The Build Process in Unix

-_Don Robinson, [ESSA](http://www.essa.com) Technologies, May 2014_
+_Don Robinson, [ESSA](http://www.essa.com) Technologies, July 2014_

 This wiki documents the process of setting things up on Unix so you can build FVS executables from the source files in the open-fvs repository. Builds of 32- and 64-bit versions have been tested using _Ubuntu Linux_. For more information on the build process, including information for builds on Windows please refer to [BuildProcess_MinGW](BuildProcess_MinGW), [BuildProcess_VisualStudio](BuildProcess_VisualStudio), or the [FAQ](FAQ). 

@@ -93,20 +93,12 @@

 When complete, you will find these 4 key components in the variant sub-directory: 

-**Component Name**
-**Language**
-
-**_FVSiec_**
-FORTRAN 
-
-**_libFVSfofem.so_**
-C 
-
-**_libFVS_iec.so_**
-FORTRAN 
-
-**_libFVSsql.so_**
-C 
+**Component Name**   | **Language**
+---------------------|--------------
+**_FVSiec_**         | FORTRAN 
+**_libFVSfofem.so_** | C 
+**_libFVS_iec.so_**  | FORTRAN 
+**_libFVSsql.so_**   | C 

 Note: When Mac OS X is used as the build environment, the `.so` suffix will be replaced with a `.dylib` suffix.

Discussion for BuildProcess_UnixAlike page

Anonymous — Fri, 10 Jul 2015 14:49:49 -0000

Originally posted by: prad...@vt.edu

Q: How to build just one variant of your choice? Answer: This is one way to do it. Please provide feedback if this is not the preferred way.

Step 1

In CMakeLists.txt find and modify the line (around line 23) that looks something like this:

file(GLOB tobuild FVSiec_sourceList.txt)

file(GLOB tobuild FVS*sourceList.txt)

modify the variant abbreviation -- iec or * in the examples above, respectively -- with the variant of your choice. For the Southern Variant (sn), here's what it looks like:

file(GLOB tobuild FVSsn_sourceList.txt)

Step 2

Save the modified CMakeLists.txt file.

Step 3

Follow the instructions above in section Building the Unix Makefile with Cmake starting with:

At the command line type

cmake -G"Unix Makefiles" .

Hope this helps. -Phil