| 1 | | If I understand correctly, many projects use "dependency tracking" so that so that incremental builds during development are faster. If you need to recompile a file, you only want to recompile that file and any of its dependencies that have changed, and not those that haven't; that's dependency tracking. Dependency tracking doesn't work with multiple `-arch` flags, for whatever reason. MacPorts automatically adds the flag [https://www.gnu.org/software/automake/manual/html_node/Dependency-Tracking.html --disable-dependency-tracking] when building universal, but this flag is only known to autotools, and feh doesn't use autotools, so we need some other way of telling it not to use dependency tracking when building universal. In fact, it would be fine to disable dependency tracking for all builds, not just universal builds, since MacPorts is generally doing a full non-incremental build anyway. |
| | 1 | If I understand correctly, many projects use "dependency tracking" so that incremental builds during development are faster. If you need to recompile a file, you only want to recompile that file and any of its dependencies that have changed, and not those that haven't; that's dependency tracking. Dependency tracking doesn't work with multiple `-arch` flags, for whatever reason. MacPorts automatically adds the flag [https://www.gnu.org/software/automake/manual/html_node/Dependency-Tracking.html --disable-dependency-tracking] when building universal, but this flag is only known to autotools, and feh doesn't use autotools, so we need some other way of telling it not to use dependency tracking when building universal. In fact, it would be fine to disable dependency tracking for all builds, not just universal builds, since MacPorts is generally doing a full non-incremental build anyway. |
