debugging - How can I capture GNUMake differences between two directories -


I have a difficult issue with gambling, when I'm made from the parent directory, something is different and the build of make all It does not necessarily and fails, but if I do the CD in the directory and fix it to make it.

How can I tell the difference between these two runs GNUmake? There should be some variables set in the parents who break the child, but I need help finding them. If you are running create from the root directory to create the text ">

> , then try make foo. If it fails, make -n foo.o to see both the directories ( print instead of to execute them) Try to run / code> what it is doing differently if it succeeds, it is also not trying to create foo.o , when run from the parent directory ; Make-N can put some light, and as the last resort build-d will give you a flow of information about the decision process, why is doing this That's what it's doing.

Here is an easy move to see the value of the variable. Place this rule in your makeup file:

  show_%: @echo $ @ $ $ ($ *)  

Now you can create show_FOO and it will give you the value of variable FOO .

Finally, do you really know that However, where you create your it.Oh files? It's great to use things to make there files here , but not in the other way, so if you are not careful then you can lose track of intermediate files. / P>


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -