[Trilinos-Announce] Trilinos dropping support for Makefile.export.* files

Carol Brickley cabrickley at hotmail.com
Fri May 21 01:07:02 MST 2021


Roscoe

I no longer work on this so please take me off the mailing list

Thanks

Carol

________________________________
From: Trilinos-Announce <trilinos-announce-bounces at trilinos.org> on behalf of Bartlett, Roscoe A <rabartl at sandia.gov>
Sent: 19 May 2021 21:06
To: trilinos-users at trilinos.org <trilinos-users at trilinos.org>; trilinos-announce at trilinos.org <trilinos-announce at trilinos.org>
Cc: 'Trilinos Framework List' <trilinos-framework at software.sandia.gov>
Subject: [Trilinos-Announce] Trilinos dropping support for Makefile.export.* files


Hello Trilinos Users,



If you are not using the installed Makefile.export.Trilinos or the package-level Makefile.export.<package> files<https://docs.trilinos.org/files/TrilinosBuildReference.html#generating-export-files>, then please ignore.



I am writing this email to announce that as part of a CMake build-system modernization effort, Trilinos will be dropping support for the installed Makefile.export.Trilinos and package-level Makefile.export.<package> files that are used by Makefile-based projects to get information to build and link against an installation of Trilinos.  The current target date for dropping support in the Trilinos ‘develop’ branch is Thursday, June 10, 2021.



The expectation is that the majority of Trilinos customer projects are (or soon will be) using CMake and can therefore use the CMake command find_package(Trilinos COMPONNETS …) or find_package(<TrilinosPackage>) that pulls in info from the installed TrilinosConfig.cmake and package-level <TrilinosPackage>Config.cmake files<https://docs.trilinos.org/files/TrilinosBuildReference.html#generating-export-files>.



An updated example project using CMake to pull in an installation of Trilinos is given in:



    https://github.com/trilinos/Trilinos/tree/master/demos/simpleBuildAgainstTrilinos



This change has been discussed in the Trilinos community for over a year with some background mentioned in:



    https://github.com/trilinos/Trilinos/issues/8498



and the technical reasons for this are discussed in:



   https://github.com/TriBITSPub/TriBITS/issues/299



If this change on this time scale will cause a significant impediment to your project, then please let us know ASAP!



Also, please forward this email to anyone who you think might be impacted by this and/or may want to provide some feedback.



Thanks,



-Ross



P.S. It is possible to bring back support for the installed Makefile.export.Trilinos and package-level Makefile.export.<package> files using a different approach after this refactoring to modern CMake.  But there needs to be a strong need from the customer community to justify this and resources will need to be allocated to implement and support this going forward.  (But the expectation is that enough of the Trilinos user community has already moved to CMake that there is not a strong need for this.)





Dr. Roscoe A. Bartlett, PhD

https://bartlettroscoe.github.io/

Sandia National Laboratories


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trilinos.org/pipermail/trilinos-announce_trilinos.org/attachments/20210521/36dd98c5/attachment-0001.html>


More information about the Trilinos-Announce mailing list