build-process

MSBuild emits the following message for up to date targets: Skipping target "MyTarget" because all output files are up-to-date with respect to the input files. How is the actual check performed? sll Check flow of Incremental Build : A target element can have both an Inputs attribute, which indicates what items the target > expects as input, and an Outputs attribute, which indicates what items it produces as output MSBuild attempts to find a 1-to-1 mapping between the values of these attributes. If a 1-to-1 mapping exists, MSBuild compares the time stamp of every input item to the time stamp of

I have a project with 5-6 libraries and one executable. The executable depends on the libraries, and some libraries depend on other libraries. How can I specify a build order so the dependencies are built before they are needed? Although this question has been answered and accepted a long time ago, I feel the need to add another answer; I honestly think that there is a better answer. I consider CONFIG += ordered harmful and a bad habit. It is probably something that was a bit prematurely introduced by the qmake developers. And there are strong opponents to its use. The drawbacks are these: it

How would you lay out the directory structure for a large C# solution, consisting of perhaps 20 to 30 projects, mostly C# but some C++? Where do you put external dependencies? When creating a branch in source control, do you branch absolutely everything? Do you override the defaults for where built files go? I'd stick with the normal "directory for the solution, each project in a subdirectory" approach - using a mixture of C# and C++ shouldn't change this. I like creating a "lib" subdirectory (off the solution directory) and put external dependencies in there, then reference that location from