<?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[Macos Bundle using CMake&#x2F;CPack]]></title><description><![CDATA[<p dir="auto">My main goal is to finallly get <a href="https://github.com/albertlauncher/albert" target="_blank" rel="noopener noreferrer nofollow ugc">albertlauncher</a> packaged for macOS. Currently i struggle to fixup the bundle. I tried macdeployqt (which complains about missing rpaths) cmake fixup_bundle (which does not deploy required plugins and the qt.conf) and the <a href="https://doc.qt.io/qt-6/cmake-commands-qtcore.html" target="_blank" rel="noopener noreferrer nofollow ugc">cmake functions of QtBase</a> (same issues as macdeployqt).</p>
<p dir="auto">The most cumbersome problem is the contradictory or outdated information online.</p>
<p dir="auto"><a href="https://github.com/albertlauncher/albert/blob/dev/CMakeLists.txt#L339" target="_blank" rel="noopener noreferrer nofollow ugc">This</a> is how far i got.</p>
<p dir="auto">What is the common practice to package the app which comprises a library, an executable (bootstrapper) and several plugins, all linking the library?</p>
<p dir="auto">Regards</p>
]]></description><link>https://forum.qt.io/topic/149323/macos-bundle-using-cmake-cpack</link><generator>RSS for Node</generator><lastBuildDate>Thu, 05 Nov 2026 03:15:03 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/149323.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 10 Sep 2023 17:33:45 GMT</pubDate><ttl>60</ttl></channel></rss>