Skip to content

Commit

Permalink
Improve reasoning for CMake complexity
Browse files Browse the repository at this point in the history
  • Loading branch information
golmschenk committed Mar 13, 2024
1 parent 321c5b0 commit 273c16e
Showing 1 changed file with 1 addition and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

0 comments on commit 273c16e

Please sign in to comment.