diff options
| author | paercebal <paercebal@gmail.com> | 2017-08-31 10:59:42 +0200 |
|---|---|---|
| committer | paercebal <paercebal@gmail.com> | 2017-08-31 10:59:42 +0200 |
| commit | e5861d356bf2b1874b74a321dcec9439a8d11ef5 (patch) | |
| tree | 5c779929497878c92bb5d11ef70fa369dcbe6a99 /docs | |
| parent | f76244f700f3ae0fe353c53c19d209589e8cdaf7 (diff) | |
| download | vcpkg-e5861d356bf2b1874b74a321dcec9439a8d11ef5.tar.gz vcpkg-e5861d356bf2b1874b74a321dcec9439a8d11ef5.zip | |
Updated the documentation to reflect the greater tolerance on configs
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/about/faq.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/about/faq.md b/docs/about/faq.md index 8234216e0..88f88bad0 100644 --- a/docs/about/faq.md +++ b/docs/about/faq.md @@ -50,7 +50,9 @@ By saving the changes to the portfile (and checking them in), you'll get the sam Yes. While Vcpkg will only produce the standard "Release" and "Debug" configurations when building a library, you can get integration support for your projects' custom configurations, in addition to your project's standard configurations. -The MSBuild $(VcpkgConfiguration) macro, if not set in your project, will identify either the "Release" or the "Debug" configuration. You only need to override this macro in your project file (.vcxproj) to declare the compatibility between your configuration, and the target standard configuration. +First of all, Vcpkg will automatically assume any custom configuration starting with "Release" (resp. "Debug") as a configuration that is compatible with the standard "Release" (resp. "Debug") configuration and will act accordingly. + +For other configurations, you only need to override the MSBuild `$(VcpkgConfiguration)` macro in your project file (.vcxproj) to declare the compatibility between your configuration, and the target standard configuration. For example, you can add support for your "MyRelease" configuration by adding in your project file: ``` |