blocks|key|820146|text|您可以将它们定义为os+environment+variables，这可能就是原始作者所做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|820147|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/ms171459.aspx^0|9|O|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can just define them as <a href="http://msdn.microsoft.com/en-us/library/ms171459.aspx">os environment variables</a>, which is probably what the original author did.

blocks|key|820211|text|property+sheet很可能是正确的解决方案；这个答案详细介绍了@gregseth，而不是试图替换它，因为它太长了，无法进行评论。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|820212|我发现我需要32位和64位目标的不同路径，这样做需要一些计算，所以我使用了documented+the+process+in+detail。|820213|我对属性表的一个关键误解是，与通常的VS属性编辑器不同，在VS属性编辑器中可以编辑不同的配置/平台组合，属性表只是一个属性列表。它没有每个配置和每个平台的子部分。这很令人困惑，因为当我向项目添加工作表时，它会出现在每个配置/平台节点下，而不是顶级项目节点下。所有的条目实际上都是针对同一个属性表文件的，所以编辑一个条目会更改所有的条目，但我最初并不理解这一点，我认为我仍然需要分别更改每个位置的值。|820214|您可以将属性表添加到一个配置/平台组合中，也可以添加到所有配置/平台组合中，也可以添加到某个子集。|820215|如果你想要有全局设置，那么配置/平台覆盖，你可以通过确保更具体的属性页是最后的来实现。因此，您可能会有一个“所有配置”属性表，一个用于"x86"，一个用于"x64“，一个用于"debug”，一个用于"release“。调试目标将具有表"all“、"x86”、“x64”。基本上是模仿VS的属性编辑器在内部执行的操作。|820216|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/669zx6zc.aspx#bkmkPropertySheets|1|https://stackoverflow.com/q/25810603/398670^0|0|E|0|0|11|W|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|14|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

A <a href="http://msdn.microsoft.com/en-us/library/669zx6zc.aspx#bkmkPropertySheets" rel="nofollow noreferrer">property sheet</a> is likely to be the right solution; this answer elaborates on @gregseth's rather than seeking to replace it, as it's too long for a comment.

I found that I needed different paths for 32-bit and 64-bit targets, and doing that took a bit of figuring out, so I've <a href="https://stackoverflow.com/q/25810603/398670">documented the process in detail</a>.

One key misunderstanding I had with property sheets was that, unlike the usual VS property editor where you can edit different configuration/platform combos, a property sheet is just a list of properties. It doesn't have per-configuration and per-platform sub-sections. That was confusing because when I added a sheet to a project it appeared under each configuration/platform node rather than under the top level project node. All the entries are actually for the same property sheet file, so editing one changes all of them, but I didn't initially understand that and thought I'd still have to change the value in each place individually.

You can add a property sheet to just one configuration/platform combo, to all of them, or to just some subset.

If you want to have global settings then configuration/platform overrides you can do so by making sure the more specific property sheets are last. So you might have a property sheet "all configurations" then one for "x86", one for "x64" one for "debug" and one for "release". The x64 debug target would have the sheets "all", "x86", "debug". Basically emulating what VS's property editor does internally.

blocks|key|820313|text|与@Serge+Rogatch的答案相同，只是我在View中找不到"Property+Manager“。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|820314|快速导航的可视化步骤：|820315|📷|atomic|offset|length|820316|​|820317|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/f2b8ed4566480de4e088ff17ce8428ef.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|V|8|@]|9|@$G|W|H|X|1|Y]]|A|$]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R|S|-4]]]]

Same answer as to @Serge Rogatch, except that I was not able to find "Property Manager" in View.

Visual steps for quick navigation:
<a href="https://i.stack.imgur.com/y4wUo.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/y4wUo.png" alt="enter image description here"></a>

blocks|key|820376|text|在2019年，您可以通过在解决方案的根目录添加Directory.Build.props+xml文件来向所有项目添加自定义宏。它们不会出现在宏部分，但如果像往常一样用$(MacroName)引用它们，则会在构建中使用它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|820377|<Project>
+<PropertyGroup>
+++<Deterministic>true</Deterministic>
+</PropertyGroup>
</Project>|code-block|syntax|javascript|820378|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build?view=vs-2019^0|N|L|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

In 2019 you can add custom macros to all of your projects by adding a <a href="https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build?view=vs-2019" rel="nofollow noreferrer">Directory.Build.props</a> xml file at the root of your solution. They don't show up in the macros section, but if referenced as usual with $(MacroName) they are used in the build.
<pre><code>&lt;Project&gt;
 &lt;PropertyGroup&gt;
 &lt;Deterministic&gt;true&lt;/Deterministic&gt;
 &lt;/PropertyGroup&gt;
&lt;/Project&gt;
</code></pre>

I just opened someone else's Visual Studio project and in their build properties they have a few custom path macro's they are using for their include and lib directories. The macro names are things like this:

<code>$(MY_WHATEVER_INCLUDE_DIR)</code>

I could manually replace every single macro with the real path, but it would be nice to just use the macros. My question is, where do I define these custom path macros at?

Visual Studio - Where to define custom path macros?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我刚刚打开了其他人的Visual Studio项目，在他们的build属性中，他们有一些自定义路径宏，用于他们的include和lib目录。宏名称如下所示：$(MY_WHATEVER_INCLUDE_DIR)我可以手动将每个宏替换为实际路径，但只使用宏会更好。我的问题是，我在哪里定义这些自定义路径宏？

问Visual Studio -在哪里定义自定义路径宏？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Visual Studio -在哪里定义自定义路径宏？EN