<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Is it wise to use C++ modules these days?]]></title><description><![CDATA[<p dir="auto">Hi,<br />
I want to start a big project. I would like to create my code using C++ modules.<br />
I did search on 'C++ modules' in this forum but did not get a good impression if modules are well supported or not.</p>
<p dir="auto">So my question is: Is it wise to use C++ module for my project? Or will I stumble into problems that I need to solve? Would it be better to keep using .h interface files for the time being?</p>
]]></description><link>https://forum.qt.io/topic/165013/is-it-wise-to-use-c-modules-these-days</link><generator>RSS for Node</generator><lastBuildDate>Tue, 22 Sep 2026 16:33:57 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/165013.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 15 Aug 2026 15:30:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Is it wise to use C++ modules these days? on Mon, 17 Aug 2026 17:16:32 GMT]]></title><description><![CDATA[<p dir="auto">Thx!<br />
Guess it is better to start with plain .cpp and .h file for now.</p>
]]></description><link>https://forum.qt.io/post/839758</link><guid isPermaLink="true">https://forum.qt.io/post/839758</guid><dc:creator><![CDATA[Simmania]]></dc:creator><pubDate>Mon, 17 Aug 2026 17:16:32 GMT</pubDate></item><item><title><![CDATA[Reply to Is it wise to use C++ modules these days? on Mon, 17 Aug 2026 07:46:25 GMT]]></title><description><![CDATA[<p dir="auto">C++ modules is still a mixed bag because the technology is not there, yet. Currently, only MSVC and CMake with the ninja generator can build programs that use modules. One of the major hurdles is that GCC (and clang?) needs several Build Module Files (BMI) depending on compiler flags. This is quite hard to manage, especially with 3rd party libraries. Additionally, you cannot easily mix e.g. std::vector or std::string from a header file and a module because they have different name mangling (there are certain tricks). So, especially for the <code>std</code> module you need to use it in all your library dependencies or not at all (or try the tricks around that).</p>
<p dir="auto">I guess modules could mostly just reduce compile times for external libraries that don't change. Basically, it gives kind of the same advantages in this area as precompiled headers (which also only work well for files that don't change). Within your own project you'll get too many dependencies that will linearize the build and thus parallel compilation might not work as well as before.</p>
<p dir="auto">BTW, there is a website where you can track which libraries support C++ modules: <a href="https://arewemodulesyet.org" target="_blank" rel="noopener noreferrer nofollow ugc">https://arewemodulesyet.org</a></p>
]]></description><link>https://forum.qt.io/post/839753</link><guid isPermaLink="true">https://forum.qt.io/post/839753</guid><dc:creator><![CDATA[SimonSchroeder]]></dc:creator><pubDate>Mon, 17 Aug 2026 07:46:25 GMT</pubDate></item><item><title><![CDATA[Reply to Is it wise to use C++ modules these days? on Sun, 16 Aug 2026 06:01:36 GMT]]></title><description><![CDATA[<p dir="auto">Don't use C++ modules for a large Qt project in 2026 — moc doesn't support them yet</p>
]]></description><link>https://forum.qt.io/post/839733</link><guid isPermaLink="true">https://forum.qt.io/post/839733</guid><dc:creator><![CDATA[Nils Sjoberg]]></dc:creator><pubDate>Sun, 16 Aug 2026 06:01:36 GMT</pubDate></item></channel></rss>