verbose build
-
Is there some sort of option in visual studio to produce a verbose build like the UNIX make command? I have a project with some sort of dependency loop, and it would be useful to know why it wants to build certain files. I know our include dependencies are messed up, and I need to track them down.
-
Is there some sort of option in visual studio to produce a verbose build like the UNIX make command? I have a project with some sort of dependency loop, and it would be useful to know why it wants to build certain files. I know our include dependencies are messed up, and I need to track them down.
-
Check the properties pages of the project, under something like Build Options.
As of how to accomplish this, have you ever tried Google?
Failing that try :badger::badger::badger:Under C/C++ - Advanced, there is a show includes option that is close to what I'm interested in. It shows a list of all of the files included by a particular source file. What I'm interested in is the ability to know which header file of that list is responsible for a particular source file being rebuilt. It's been years since I ran makefiles under UNIX, but I remember having this ability.
-
Under C/C++ - Advanced, there is a show includes option that is close to what I'm interested in. It shows a list of all of the files included by a particular source file. What I'm interested in is the ability to know which header file of that list is responsible for a particular source file being rebuilt. It's been years since I ran makefiles under UNIX, but I remember having this ability.
-
Hmm, I've actually had a look for a verbose setting but can't find it now. Where the hell did I see it from? :sigh: Probably a Linux compiler :doh:
As of how to accomplish that have you ever tried Google? Failing that try :badger::badger::badger:.
-
Is there some sort of option in visual studio to produce a verbose build like the UNIX make command? I have a project with some sort of dependency loop, and it would be useful to know why it wants to build certain files. I know our include dependencies are messed up, and I need to track them down.
rentzk wrote:
I know our include dependencies are messed up, and I need to track them down.
Have you tried turning on the verbose switch in the complier? /VERBOSE (Print Progress Messages)[^]
I'd love to help, but unfortunatley I have prior commitments monitoring the length of my grass. :Andrew Bleakley:
-
Hmm, I've actually had a look for a verbose setting but can't find it now. Where the hell did I see it from? :sigh: Probably a Linux compiler :doh:
As of how to accomplish that have you ever tried Google? Failing that try :badger::badger::badger:.