問題描述
我已經閱讀了關于Custom.Before.Microsoft.Common.targets"和Custom.After.Microsoft.Common.targets"的使用,以便在每個項目構建之前/之后執行自定義目標,我會喜歡使用這種技術來在我們的 TeamCity 構建服務器上構建時更改版本信息.
I've read about the use of "Custom.Before.Microsoft.Common.targets" and "Custom.After.Microsoft.Common.targets" in order to execute a custom target before/after every project build and I would like to use this technique in order to change version info while building on our TeamCity build server.
問題是,雖然它適用于 C# 項目,但它似乎不適用于本機 C++ 項目.
The problem is that although it works for C# projects, it doesn't seem to work for native C++ projects.
在 Microsoft.Cpp.targets 文件中進行一些挖掘后,我發現對于本機 C++ 項目,這似乎是通過設置 $(ForceImportBeforeCppTargets) 和 $(ForceImportAfterCppTargets) 來實現的.
After some digging around in the Microsoft.Cpp.targets file I found out that for native C++ projects this seems to be implemented through setting $(ForceImportBeforeCppTargets) and $(ForceImportAfterCppTargets).
不過,我似乎無法在網絡上找到有關本機 C++ 應用程序的這項技術的一條信息,所以我在問我是否在尋找正確的方向.
I can't seem to find a single piece of information on the web about this technique for native C++ apps though, so I'm asking if I'm looking in the right direction or not.
感謝任何幫助.
推薦答案
對于 VC++ 項目來說有點不同.您可以在項目開始或結束時定義要導入的文件.要使用此方法,您需要為屬性 ForceImportBeforeCppTargets
或 ForceImportAfterCppTargets
定義值.例如,如果您希望在項目的開頭包含一個文件,您可以在命令行中傳遞該值.例如,我剛剛創建了一個名為 CppTets??01 的虛擬 VC++ 項目.然后我創建了下面的兩個示例文件.
For VC++ projects it is a bit different. You define a file to be imported either at the beginning or at the end of the project. To use this approach you need to define values for the properties ForceImportBeforeCppTargets
or ForceImportAfterCppTargets
. For example if you want a file to be included at the beginning of the project you can pass in the value at the command line. For example I just created a dummy VC++ project named CppTets01. Then I created the two sample files below.
Before.proj
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Target Name="CustomTargetInBefore" AfterTargets="Build">
<Message Text="From CustomTargetInBefore" Importance="high"/>
</Target>
</Project>
After.proj
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<Target Name="CustomTargetInAfter" AfterTargets="Build">
<Message Text="From CustomTargetInAfter" Importance="high"/>
</Target>
</Project>
然后我執行了以下命令:
Then I executed the following command:
msbuild CppTest01.vcxproj
/p:ForceImportBeforeCppTargets="C:Temp\_NETThrowAwayCppTest01CppTest01Before.proj";
ForceImportAfterCppTargets="C:Temp\_NETThrowAwayCppTest01CppTest01After.proj"
結果是C:Temp_NETThrowAwayCppTest01CppTest01>msbuild CppTest01.vcxproj/p:ForceImportBeforeCppTargets="C:Temp_NETThrowAwayCppTest01CppTest01Before.proj";ForceImportAfterCppTargets="C:Temp_NETThrowAwayCppTest01CppTest01After.proj"
The result was C:Temp_NETThrowAwayCppTest01CppTest01>msbuild CppTest01.vcxproj /p:ForceImportBeforeCppTargets="C:Temp_NETThrowAwayCppTest01C ppTest01Before.proj";ForceImportAfterCppTargets="C:Temp_NETThrowAwayCppTest01CppTest01After.proj"
Microsoft (R) Build Engine Version 4.0.30319.1
[Microsoft .NET Framework, Version 4.0.30319.1]
Copyright (C) Microsoft Corporation 2007. All rights reserved.
Build started 10/18/2010 8:32:55 AM.
Project "C:Temp\_NETThrowAwayCppTest01CppTest01CppTest01.vcxproj" on node 1 (default targets).
InitializeBuildStatus:
Creating "DebugCppTest01.unsuccessfulbuild" because "AlwaysCreate" was specified.
ClCompile:
All outputs are up-to-date.
All outputs are up-to-date.
ManifestResourceCompile:
All outputs are up-to-date.
Link:
All outputs are up-to-date.
Manifest:
All outputs are up-to-date.
FinalizeBuildStatus:
Deleting file "DebugCppTest01.unsuccessfulbuild".
Touching "DebugCppTest01.lastbuildstate".
CustomTargetInBefore:
From CustomTargetInBefore
CustomTargetInAfter:
From CustomTargetInAfter
Done Building Project "C:Temp\_NETThrowAwayCppTest01CppTest01CppTest01.vcxproj" (default targets).
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.21
從輸出中可以看出,目標已成功注入到構建過程中.如果您想將其與 Custom.Before.Microsoft.Common.targets
和 Custom.Before.Microsoft.Common.targets
聯系起來,那么您應該知道那里使用的技術有點不同.特別是如果您創建這些文件,它們會自動導入到每個 C#/VB.NET 項目中.在這種情況下,您必須設置此屬性.你真的有兩個選擇:
As you can see from the output the targets were successfully injected into the build process. If you want to relate this back to Custom.Before.Microsoft.Common.targets
and Custom.Before.Microsoft.Common.targets
then you should know that the technique used there is a bit different. Specifically if you create those files they are automatically imported into every C#/VB.NET project. In this case you have to set this property. You really have two options here:
- 您可以將此屬性設置為環境變量
- 您可以使用另一種技術,ImportBefore &VC++特有的ImportAfter
對于#1,讓我解釋一下.在 MSBuild 中,當您使用語法 $(PropName) 訪問屬性時,如果名稱為 PropName 的屬性不存在,MSBuild 將在環境變量中查找是否存在這樣的值,如果存在,則返回該值.因此,如果您有一個構建服務器,您希望在其中為每個 VC++ 構建包含一個文件,那么只需將這些屬性創建為環境變量.現在是另一種技術.
For #1 let me explain a bit. In MSBuild when you access a property with the syntax $(PropName) then if a property with the name PropName doesn't exist MSBuild will look up in the environment variables to see if such a value exists, if it does then that value is returned. So if you have a build server in which you want to include a file for each VC++ build, then just create those properties as environment variables. Now for the other technique.
ImportBefore/ImportAfter在 VC++ 中引入了一個新概念.在 Microsoft.Cpp.Win32.targets 中,您可以看到 .targets 文件頂部的聲明.
ImportBefore/ImportAfter In VC++ a new concept is introduced. In Microsoft.Cpp.Win32.targets you can see the declaration at the top of the .targets file.
<Import Project="$(VCTargetsPath)PlatformsWin32ImportBefore*.targets"
Condition="Exists('$(VCTargetsPath)PlatformsWin32ImportBefore')" />
然后有一個朝向底部
<Import Project="$(VCTargetsPath)PlatformsWin32ImportAfter*.targets"
Condition="Exists('$(VCTargetsPath)PlatformsWin32ImportAfter')" />
其他目標平臺也存在類似的導入聲明.查看 %ProgramFiles32%MSBuildMicrosoft.Cppv4.0Platforms
中的文件以了解具體名稱.
A similar import declaration exists for the other target platforms as well. Take a look at the files at %ProgramFiles32%MSBuildMicrosoft.Cppv4.0Platforms
for the specific names.
如果您想要導入文件,則使用此技術只需創建一個以 .targets
結尾的文件并將其放入適當的文件夾中.這樣做的好處是它將被導入到該平臺的每個 VC++ 構建中,并且您可以創建許多不同的文件.缺點是您必須將它們放在那些特定的文件夾中.這是兩種技術之間的主要區別.使用第一種技術,您可以通過屬性指定文件位置,它不會自動包含在每個構建中,但對于第二種方法,您不能更改位置
With this technique if you want a file to be imported then simply create a file that ends with .targets
and place it into the appropriate folder. The advantage of this is that it will be imported into every VC++ build for that platform, and that you can create many different files. The drawback is that you have to place them in those specific folders. That's the main difference between both techniques. With this first technique you can specify the file location via property and its not automatically included for every build, but for the second approach it is but you cannot change the location
這篇關于MSBuild:用于 VS2010 中本機 C++ 項目的 Custom.After.Microsoft.Common.targets的文章就介紹到這了,希望我們推薦的答案對大家有所幫助,也希望大家多多支持html5模板網!