Improve reasoning for CMake complexity

golmschenk · golmschenk · commit 273c16ecfa0a · 2024-03-12T23:24:48.000-04:00
diff --git a/docs/source/developer_guides/guide_for_fortran_developers.md b/docs/source/developer_guides/guide_for_fortran_developers.md
@@ -61,4 +61,4 @@ prior to the build commands.
 
 ## Adding source files
 
-The file specifying which source files to compile, `CMakeLists.txt`, may look somewhat confusing to those unfamiliar to CMake, especially due to the complexity added by importing remote GitHub dependencies and building both a Python library and the main binary executable. For Fortran developers, the main piece you will likely need to change is to add additional source files to be compiled. In most cases, you should add your new source files to the statement starting with `add_executable(eesunhong_main`. If the source files will include functions or routines that should be callable from Python, they should generally be included in the statement starting with `add_library(eesunhong_internal`.
+The file specifying which source files to compile, `CMakeLists.txt`, may look somewhat confusing to those unfamiliar to CMake, especially due to the complexity added by importing remote GitHub dependencies, using multiple source languages, and building both a Python library and the main binary executable. For Fortran developers, the main piece you will likely need to change is to add additional source files to be compiled. In most cases, you should add your new source files to the statement starting with `add_executable(eesunhong_main`. If the source files will include functions or routines that should be callable from Python, they should generally be included in the statement starting with `add_library(eesunhong_internal`.

Original file line number	Diff line number	Diff line change
`@@ -61,4 +61,4 @@ prior to the build commands.`
`61`	`61`
`62`	`62`	`## Adding source files`
`63`	`63`
`64`		-The file specifying which source files to compile, `CMakeLists.txt`, may look somewhat confusing to those unfamiliar to CMake, especially due to the complexity added by importing remote GitHub dependencies and building both a Python library and the main binary executable. For Fortran developers, the main piece you will likely need to change is to add additional source files to be compiled. In most cases, you should add your new source files to the statement starting with `add_executable(eesunhong_main`. If the source files will include functions or routines that should be callable from Python, they should generally be included in the statement starting with `add_library(eesunhong_internal`.
	`64`	+The file specifying which source files to compile, `CMakeLists.txt`, may look somewhat confusing to those unfamiliar to CMake, especially due to the complexity added by importing remote GitHub dependencies, using multiple source languages, and building both a Python library and the main binary executable. For Fortran developers, the main piece you will likely need to change is to add additional source files to be compiled. In most cases, you should add your new source files to the statement starting with `add_executable(eesunhong_main`. If the source files will include functions or routines that should be callable from Python, they should generally be included in the statement starting with `add_library(eesunhong_internal`.