Formaline always triggeres new link

Comments (6)

1. 

   Erik Schnetter

   • removed comment

   A new executable is built because Formaline records the build time and date into a unique identifier that identifies this build. This identifier changes, and hence a very small file is recompiled. This also triggers the linking stage.

   Cactus itself also records the time and date of the build into a file datestamp.c. Maybe moving Formaline's identifiers into this file would solve this issue.

   • 2013-01-18T08:54:02+00:00
2. 

   Frank Löffler reporter

   • removed comment

   datestamp.c is only compiled if the linking actually happens. There is a special rule for that in the Cactus make system (actually not even a real rule - it is part of the linking phase). I would expect that either moving this part of Formaline into that file, or making Cactus aware of other files that only need to be compiled if linking needs to be done.

   • 2013-01-18T09:10:06+00:00
3. 

   Roland Haas

   Pull request is here: https://bitbucket.org/cactuscode/cactusutils/pull-requests/23/rhaas-speedup

   • 2019-06-30T00:45:34+00:00
4. 

   Roland Haas

   • edited description
   • changed status to open

   Please review.

   • 2019-06-30T00:45:46+00:00
5. 

   Roland Haas

   Unless objected I will push after 2019-11-26.

   • 2019-11-12T21:58:47+00:00
6. 

   Roland Haas

   • changed status to resolved

   Applied as git hash 2c7f53b "Formaline: only create new build id if something changed" of cactusutils

   • 2019-11-27T16:00:10+00:00
7. Log in to comment