Wednesday, 15 February 2012

c - What is the use case for -M gcc option? -


The GCC's -M option provides a consistent list of dependency makeup. I have a project *. C files and I got a very long list of various system headers:

  $ gcc -i / home / marko / foo / local / include -i / home / Marko / foo / src / misc.git -M src / foo.c | WC-L 65  

What are the use cases for this? Why do not anyone need such a long list of such useful dependency? Or is it used in any type of autotools and does not mean for manual use?

I think this is primarily a pendant, cheese. You may want to track system dependency for some reason, for example, you are using - system or - sysroot or something else, and your dependency tracking You want to work properly when you update the files in sysroot

I guess using -M is usually harmless.

/ div>

No comments:

Post a Comment