<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The relevant documentation regarding the behavior of the VS generator is here:<div class=""><br class=""></div><div class=""><a href="https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html" class="">https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html</a></div><div class=""><br class=""></div><div class="">The relevant quote is:</div><div class=""><br class=""></div><div class="">"This variable is only meaningful to single-configuration generators (such as Makefile Generators and Ninja) i.e. those which choose a single configuration when CMake runs to generate a build tree as opposed to multi-configuration generators which offer selection of the build configuration within the generated build environment."</div><div class=""><br class=""></div><div class="">-Chris<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 19, 2018, at 7:06 AM, Dennis Luehring via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">thx for the help - debug and release version is built<br class=""><br class="">Am 19.09.2018 um 13:21 schrieb Dennis Luehring via llvm-dev:<br class=""><blockquote type="cite" class="">beware of small trap:<br class=""><br class="">cmake --build . --config Release<br class=""><br class="">works<br class=""><br class="">cmake --config Release --build .<br class=""><br class="">breaks after does not build - leaves build without errors<br class=""><br class="">Am 19.09.2018 um 11:03 schrieb Dennis Luehring via llvm-dev:<br class="">> >because with that generator the CMAKE_BUILD_TYPE variable is ignored<br class="">> >because it is a "multi-configuration target".<br class="">><br class="">> thanks for the link, is that a bug in the CMake configuration (or better<br class="">> not getting any warning) or is there just documentation missing?<br class="">><br class="">> so i can use --config Debug or --config Release and get the correct<br class="">> results - i hope that works the build takes hours<br class="">><br class="">> strange is that -DCMAKE_BUILD_TYPE=Debug results in a different<br class="">> build-directory size compared to -DCMAKE_BUILD_TYPE=Release - so its not<br class="">> fully ignored?<br class="">><br class="">> Am 19.09.2018 um 10:30 schrieb <a href="mailto:Boldizsar.Palotas@esa.int" class="">Boldizsar.Palotas@esa.int</a>:<br class="">> > If I understand correctly, you need to set Release mode within the VS IDE<br class="">> > because with that generator the CMAKE_BUILD_TYPE variable is ignored<br class="">> > because it is a "multi-configuration target".<br class="">> ><br class="">> > see<br class="">> > <a href="https://stackoverflow.com/questions/24460486/cmake-build-type-not-being-used-in-cmakelists-txt" class="">https://stackoverflow.com/questions/24460486/cmake-build-type-not-being-used-in-cmakelists-txt</a><br class="">> ><br class="">> ><br class="">> ><br class="">> > From: Dennis Luehring via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>><br class="">> > To: llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>><br class="">> > Date: 2018.09.19 06:11<br class="">> > Subject: [llvm-dev] CMake build of LLVM/clang with<br class="">> > -DCMAKE_BUILD_TYPE=Release does not create release versions?<br class="">> > Sent by: "llvm-dev" <<a href="mailto:llvm-dev-bounces@lists.llvm.org" class="">llvm-dev-bounces@lists.llvm.org</a>><br class="">> ><br class="">> ><br class="">> ><br class="">> > my build environment:<br class="">> ><br class="">> > Win7 x64<br class="">> > VStudio 2017 Community Edition 15.8.4 (latest)<br class="">> > CMake 3.12.1 (x86)<br class="">> > git 2.19.0 (latest, x64)<br class="">> > Python 2.7.2 (x86)<br class="">> ><br class="">> > directory structure<br class="">> ><br class="">> > test<br class="">> > llvm <-- git clone <a href="https://github.com/llvm-mirror/llvm" class="">https://github.com/llvm-mirror/llvm</a><br class="">> > tools<br class="">> > clang <-- git clone <a href="https://github.com/llvm-mirror/clang" class="">https://github.com/llvm-mirror/clang</a><br class="">> > llvm_build<br class="">> ><br class="">> > Debug build: clean build, llvm_build is deleted before<br class="">> ><br class="">> > llvm_build> cmake -Thost=x64 -G "Visual Studio 15 2017 Win64"<br class="">> > -DCMAKE_BUILD_TYPE=Debug -DLLVM_TARGETS_TO_BUILD=host<br class="">> > -DLLVM_BUILD_EXAMPLES=1 -DCLANG_BUILD_EXAMPLES=1<br class="">> > -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_DOCS=OFF ..\llvm<br class="">> ><br class="">> > builds for hours, a few warning, no errors -> llvm_build is ~44GB<br class="">> ><br class="">> > i can find many working libs/exes(also examples) in<br class="">> > llvm_build\Debug\(lib|bin)<br class="">> ><br class="">> > then i tried to build release versions<br class="">> ><br class="">> > Release build: clean build, llvm_build is deleted before<br class="">> ><br class="">> > llvm_build> cmake -Thost=x64 -G "Visual Studio 15 2017 Win64"<br class="">> > -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=host<br class="">> > -DLLVM_BUILD_EXAMPLES=1 -DCLANG_BUILD_EXAMPLES=1<br class="">> > -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_DOCS=OFF ..\llvm<br class="">> ><br class="">> > builds for hours, a few warning, no errors -> llvm_build is ~47GB (i<br class="">> > though Release would be smaller?)<br class="">> ><br class="">> > i can find many working libs/exes(also examples) in<br class="">> > llvm_build\Debug\(lib|bin) - the executables seems to be larger as in<br class="">> > "Debug"-Build?<br class="">> ><br class="">> > llvm-build\Release\bin just contains llvm-lit.py<br class="">> ><br class="">> > why is the debug folder populated and where i can find the Release build<br class="">> > libs/exes?<br class="">> ><br class="">> ><br class="">> > _______________________________________________<br class="">> > LLVM Developers mailing list<br class="">> > <a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">> > <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class="">> ><br class="">> ><br class="">> ><br class="">> > This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<br class="">> > protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<br class="">> > this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<br class="">> > personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int" class="">dpo@esa.int</a>).<br class="">> ><br class="">> ><br class="">><br class="">> _______________________________________________<br class="">> LLVM Developers mailing list<br class="">> <a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br class=""><br class=""><br class="">_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></blockquote><br class=""><br class="">_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></div></blockquote></div><br class=""></div></body></html>