This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
So what about using the output of gcc -MM (or one of the other -M>options?) to generate dependencies in the source directory, like BFD >does?
How is embedding this stuff in the source directory better?
Because it doesn't need to rely on assumptions about the GDB coding style, and it doesn't require parsing all the source files when we configure?
It's like regenerating configure; we try not to run autoconf during the build process, and not just because autoconf is so finicky.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |