On 06/11/2017 17:23, Sebastian Huber wrote: > How reliable is this Autoconf stuff?
Haha, that is a leading question! I suppose it depends on how you use it or abuse it as we have in our case. > Do I have to re-build everything after each > Git checkout (cpuopts.h is included in nearly every header)? The hash is only updated when configure is run. It is not 100% full proof, something like a makefile check or the post-checkout would be needed if that path is taken. What I did was a "good attempt" at best. > Why can't we use a Git post-checkout hook (attached)? I tend to get a little uneasy when a VC tool is touching code in a project underneath another operation. It makes auditing more complicated. If you think the autoconf change is still not suitable I suppose something in the makefiles could perform the post-checkout functionality. We need a way for the build and test records to show what was being tested. We currently lack that information. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
