VS 2010 - project dependencies.
in [MFC]
|
Prev: open .chm file from VC++ - with Table Of Contents hidden - HTMLHel
Next: How can I assign a size to a What's This popup help window?
From: David Webber on 2 Jun 2010 04:54 "David Ching" <dc(a)remove-this.dcsoft.com> wrote in message news:A3A66C7F-13DF-4B89-858B-9A17DA279E04(a)microsoft.com... > "David Webber" <dave(a)musical-dot-demon-dot-co.uk> wrote in message > news:uQ5du6YALHA.980(a)TK2MSFTNGP04.phx.gbl... >> After building, two of my DLLs are not registering as up to date, and a >> subsequent build links them again. Another three are fine. >> > > This move to MSBuild is causing some issues. It works differently than > previous VC++. Go into Options | Projects and Solutions | Build and Run | > MSBuild Project Build Output Verbosity and crank it up. You should then > get diagnostic messages in the Output window about why rebuilds happen. Thanks, Doing this to a level which gives more information but not so much that I drown in it says, when it comes to mzw32n.dll: "Creating "Debug\mzw32n.unsuccessfulbuild" because "AlwaysCreate" was specified." The question is now, how was AlwaysCreate specified in the project properties dialogue? The help system gives 9 references when I search for AlwaysCreate but most don't seem to have any relevance at all to building Visual Studio projects. One or two relate to "MSBuild tasks" but then, apart form one or two things looking vaguely like the gobbledygook in the .vcxproj XML file, I'm lost :-( I thought the project properties dialogue was so you didn't have to know about the format of that not-very-human-readable file? Dave -- David Webber Mozart Music Software http://www.mozart.co.uk For discussion and support see http://www.mozart.co.uk/mozartists/mailinglist.htm
From: David Webber on 2 Jun 2010 05:15 "David Webber" <dave(a)musical-dot-demon-dot-co.uk> wrote in message news:#FLXeFjALHA.4652(a)TK2MSFTNGP06.phx.gbl... > "Creating "Debug\mzw32n.unsuccessfulbuild" because "AlwaysCreate" was > specified." > > The question is now, how was AlwaysCreate specified in the project > properties dialogue? In more detail: Creating "Debug\mzw32m.unsuccessfulbuild" because "AlwaysCreate" was specified. 2>ClCompile: 2> All outputs are up-to-date. 2> All outputs are up-to-date. 2> All outputs are up-to-date. 2>ResourceCompile: 2> All outputs are up-to-date. 2>ManifestResourceCompile: 2> All outputs are up-to-date. 2>Link: 2> All outputs are up-to-date. 2>Manifest: 2> All outputs are up-to-date. 2> All outputs are up-to-date. 2>FinalizeBuildStatus: 2> Deleting file "Debug\mzw32m.unsuccessfulbuild". 2> Touching "Debug\mzw32m.lastbuildstate". 2> 2>Build succeeded. It looks like the build is being marked as up to date, but something is telling the builder to take no notice of that. Dave -- David Webber Mozart Music Software http://www.mozart.co.uk For discussion and support see http://www.mozart.co.uk/mozartists/mailinglist.htm
From: David Ching on 2 Jun 2010 09:32 "David Webber" <dave(a)musical-dot-demon-dot-co.uk> wrote in message news:#FLXeFjALHA.4652(a)TK2MSFTNGP06.phx.gbl... > "Creating "Debug\mzw32n.unsuccessfulbuild" because "AlwaysCreate" was > specified." > This might be OK, don't know how to change it anyway. Are you seeing anything like: C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(1151,5): warning MSB8012: TargetPath(C:\Users\Sol0\Desktop\fltk-1.1.10\vcnet\.\Debug\jpeg.lib) does not match the Library's OutputFile property value (C:\Users\Sol0\Desktop\fltk-1.1.10\lib\fltkjpegd.lib). This may cause your project to build incorrectly. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Lib.OutputFile). Some of my projects generated this message when converted, and I'm still investigating how the project might "build incorrectly". -- David
From: David Webber on 2 Jun 2010 12:34
"David Ching" <dc(a)remove-this.dcsoft.com> wrote in message news:63B6A5CE-6493-41A3-BB84-7765DD7A2CCB(a)microsoft.com... > "David Webber" <dave(a)musical-dot-demon-dot-co.uk> wrote in message > news:#FLXeFjALHA.4652(a)TK2MSFTNGP06.phx.gbl... >> "Creating "Debug\mzw32n.unsuccessfulbuild" because "AlwaysCreate" was >> specified." >> > > This might be OK, don't know how to change it anyway. > > Are you seeing anything like: > > C:\Program > Files\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(1151,5): > warning MSB8012: > TargetPath(C:\Users\Sol0\Desktop\fltk-1.1.10\vcnet\.\Debug\jpeg.lib) does > not match the Library's OutputFile property value > (C:\Users\Sol0\Desktop\fltk-1.1.10\lib\fltkjpegd.lib). This may cause your > project to build incorrectly. To correct this, please make sure that > $(OutDir), $(TargetName) and $(TargetExt) property values match the value > specified in %(Lib.OutputFile). I was, and I hoped getting rid of them would do the trick. Setting the linker output to $(OutDir)$(TargetName)$(TargetExt) seems to make it agree with the general properties (which I am guessing defines $(OutDir)) and I think the above messages went away when I did that... > Some of my projects generated this message when converted, and I'm still > investigating how the project might "build incorrectly". ...but I am still getting those two DLLs linking when they don't need to. Dave -- David Webber Mozart Music Software http://www.mozart.co.uk For discussion and support see http://www.mozart.co.uk/mozartists/mailinglist.htm |