From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BAAE13858C42; Sat, 30 Dec 2023 16:34:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BAAE13858C42 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1703954059; bh=Fa1L0/PwbfM4dCj1cBbqRFX51JVa6qSMn1AO5/QOKCk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=kSTyAH9sNMJnJksU8lGb4tpiBG/1JO0aieoDpWafjnZn6gUOy/rBvKr/YCgMLZ1ID SJaN4FzFMAgQdUpWHTohYOkx1dBTt6yQTJE6GRMwYOSUYCUaxLtCz1vq4EeCGCkD/f XhecUbv65NnzFEVhMZ1NBVIPva2hEfhCNQPI+fok= From: "jpakkane at gmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 11.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jpakkane at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105467 --- 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 person= al experience almost everybody uses CMake's Ninja backend rather than the Make backend on unixy platforms simply because it is so much faster=20 CMake does not support modules in the Make backend [2]. Some people even cl= aim that properly supporting Make to build C++ modules is not possible if you w= ant to make it actually production quality and reliable. Modules are very much a forward looking thing. People who still use plain M= ake are most likely doing so on legacy projects that can not adopt modules in t= he 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=