[Nouveau] [Mesa3d-dev] makedepend in Mesa
chantry.xavier at gmail.com
Thu Feb 25 11:18:50 PST 2010
On Tue, Feb 23, 2010 at 11:14 PM, Dan Nicholson <dbn.lists at gmail.com> wrote:
> We could use gcc directly for depends (I have a patch to do it), but:
> 1. I don't think it would actually help much in terms of rebuilds
> since makedepend seems to do a perfectly adequate job of finding the
> needed headers.
> 2. gcc expects to output a single make target for a single source
> file. mesa just tosses all the source files at makedepend which
> generates a depend file with a bunch of targets. gcc is phenomenally
> slow doing the same. Changing the build to include one dep file per
> source file would be a ton of churn.
> 3. The fast way automake does gcc dep tracking is to do it as a step
> during the compile. Since gcc fully preprocesses the source file
> before generating the make target, you can get it for free during the
> compile. Doing as a separate step like mesa means you're throwing away
> the preprocessing and then doing it again immediately afterward. The
> time adds up.
> I guess what I'm saying is that I wouldn't bother with gcc dep
> tracking unless it's coming as part of automake.
Thanks for all these explanations !
> configure checks for makedepend, but doesn't error if it's not found.
> It probably should. Likewise, the commands running makedepend should
> probably not be silenced with stderr redirected to /dev/null. That
> would break builds for people using the static configs without
Why do we need static configs ?
If I understand correctly, we have the choice between 1 autoconf file,
and more than 100 static config files ?
And autoconf can potentially capture all these static configurations and more ?
> I think the problem is more that it's not used consistently since it
> has to be setup manually in the Makefile vs. automatically like
My understanding of autotools is still very limited. mesa currently
doesn't use automake, does it ?
A git grep automake lets me believe that it was dropped in 5.1
So currently makedepend needs to be setup manually in all the Makefiles ?
And using automake would give a big advantage on the two sides :
1) automatic makedepend setup
2) efficient use of gcc dep tracking
> I'd be comfortable having makedepend be a hard requirement in
> configure. Otherwise, I'd rather have this be AC_MSG_WARN([your
> message]) right after the AC_PATH_PROG for makedepend.
Actually I wanted to propose a hard requirement but then thought some
people might complain.
If I just put a AC_MSG_WARN right after AC_PATH_PROG, I am afraid it
won't make a big difference as it won't be very visible.
To make a hard requirement, I could just use AC_MSG_ERROR instead ?
[I wonder if it wouldn't be easier to make scons work like I want to
avoid all these problems.
I believe I would just need to add nouveau support, and probably look
into this :
# TODO: Build several variants at the same time?
diff --git a/configure.ac b/configure.ac
index 485836a..a582337 100644
@@ -28,8 +28,11 @@ AC_PROG_CPP
AC_CHECK_PROGS([MAKE], [gmake make])
+AC_PATH_PROG([MKDEP], [makedepend], no)
+if test "x$MKDEP" = xno; then
+ AC_MSG_ERROR([makedepend not found])
dnl Our fallback install-sh is a symlink to minstall. Use the existing
dnl configuration in that case.
More information about the Nouveau