Skip to content

CMake: Make libint2 Fortran interface explicit - #423

Open
Growl1234 wants to merge 4 commits into
evaleev:masterfrom
Growl1234:cmake-fortran
Open

CMake: Make libint2 Fortran interface explicit#423
Growl1234 wants to merge 4 commits into
evaleev:masterfrom
Growl1234:cmake-fortran

Conversation

@Growl1234

Copy link
Copy Markdown
Contributor

Libint2 currently installs the libint_f.mod module file without exporting a corresponding CMake target. As a result, downstream projects have to locate compiler-specific Fortran module directories manually.

Introduce an installable int_f wrapper library, exported as Libint2::int_f. Linking this target provides the Fortran wrapper library, the underlying Libint2 library, and the correct module include directory through its usage requirements.

The Fortran module installation directory is now controlled by CMAKE_INSTALL_Fortran_MODULES, defaulting to the existing include-directory location. Distribution packages (Fedora RPM-build) can override it at configure time, avoiding post-install relocation of libint_f.mod.

This allows downstream projects to consume the Fortran interface through the exported package metadata rather than searching for libint_f.mod themselves.

evaleev and others added 3 commits August 13, 2026 17:01
Follow-up to the Libint2 Fortran interface work in this branch:

* decide PIC for the libint_f objects from L2_BUILD_SHARED_LIBS rather
  than BUILD_SHARED_LIBS, matching int-obj. With
  LIBINT2_BUILD_SHARED_AND_STATIC_LIBS=ON and BUILD_SHARED_LIBS=OFF the
  now-installed libint2_f.a was built without -fPIC while
  interface-linking the shared libint2.

* install the generated Fortran headers (fortran_incldefs.h,
  libint2_types_f.h) into <includedir>/libint2/fortran and add that
  directory to the target's INSTALL_INTERFACE. fortran_example.F90,
  the canonical consumer example, #includes fortran_incldefs.h, so
  downstream users of the installed target could not compile.

* name the public consumption target Libint2::fortran, as INSTALL.md
  already advertised, aliased to int_f in the build tree and in
  libint2-config.cmake, the same way Libint2::int2 and Libint2::cxx are
  handled. int_f remains the exported internal target. This also makes
  a namespaced name available to add_subdirectory/FetchContent users.

* rename CMAKE_INSTALL_Fortran_MODULES to LIBINT2_INSTALL_FMODDIR and
  make it a cache entry, out of the reserved CMAKE_ namespace. It is
  declared the way GNUInstallDirs declares its own path variables,
  because a plain set(... CACHE PATH) rewrites a relative -D value into
  an absolute path below the build directory.

* forward LIBINT2_INSTALL_FMODDIR to the library ExternalProject and add
  it to the staging-area install directories, so the packaging use case
  works in the one-shot generator + library build.

* resolve the fortran component from the imported target instead of the
  configure-time option, deferring check_required_components() until
  after the targets file is included, and move its doc line out of the
  ordering-code table.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants