[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Diffing the results of conifgure
From: |
Philip Prindeville |
Subject: |
Diffing the results of conifgure |
Date: |
Sun, 25 Jul 2010 13:51:55 -0600 |
User-agent: |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 |
Hi.
We're passing a lot of information into configure manually because a lot of
packages didn't used to handle cross-compilation correctly, but lately those
packages have been getting better.
We'd like to start to peel away options that we pass to configure.
But, to ensure that the results are still correct, we'd want to capture the summary of results and diff files
together, a "before" and "after" changes to our build infrastructure to make sure that
the outputs are now discovered as the correct values, rather than being "forced" from the command
line or environment.
confdefs.h is one idea, but I'm not sure it captures *all* of the state. Does
it?
config.log and config.status are too wordy, and their output can vary (based on
autoconf versions) yet still come up with the correct final result, so those
seem unlikely (unless we just extract the relevant portions of these).
What's the collective wisdom of the group?
Thanks,
-Philip
- Diffing the results of conifgure,
Philip Prindeville <=