public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jpakkane at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105467] Dependency file produced by C++ modules causes Ninja errors Date: Sat, 30 Dec 2023 16:34:12 +0000 [thread overview] Message-ID: <bug-105467-4-1L70mh5JCc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105467-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105467 --- Comment #6 from jpakkane at gmail dot com --- According to C++ foundation's developer survey [1] the most popular build system for C++ projects is CMake by quite a massive margin. Based on personal experience almost everybody uses CMake's Ninja backend rather than the Make backend on unixy platforms simply because it is so much faster CMake does not support modules in the Make backend [2]. Some people even claim that properly supporting Make to build C++ modules is not possible if you want to make it actually production quality and reliable. Modules are very much a forward looking thing. People who still use plain Make are most likely doing so on legacy projects that can not adopt modules in the near future in any case. Thus it would seem that the most probable ways C++ modules are going to be used are a) VS projects b) whatever Xcode ends up implementing c) Ninja files. [1] https://isocpp.org/files/papers/CppDevSurvey-2023-summary.pdf [2] https://cmake.org/cmake/help/latest/manual/cmake-cxxmodules.7.html
next prev parent reply other threads:[~2023-12-30 16:34 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-03 15:04 [Bug c++/105467] New: " jpakkane at gmail dot com 2023-10-18 1:32 ` [Bug c++/105467] " bugzilla.gcc at me dot benboeckel.net 2023-10-20 19:55 ` jpakkane at gmail dot com 2023-12-23 4:38 ` saifi.khan at nishan dot io 2023-12-30 14:18 ` jpakkane at gmail dot com 2023-12-30 15:04 ` pinskia at gcc dot gnu.org 2023-12-30 16:34 ` jpakkane at gmail dot com [this message] 2023-12-30 18:11 ` pinskia at gcc dot gnu.org 2023-12-30 19:15 ` bugzilla.gcc at me dot benboeckel.net 2023-12-30 19:16 ` bugzilla.gcc at me dot benboeckel.net
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-105467-4-1L70mh5JCc@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).