zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

731
active users

#meson

0 posts0 participants0 posts today
🔗 David Sommerseth<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@underseamonkey" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>underseamonkey</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.org.uk/@Waxingtonknee" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Waxingtonknee</span></a></span> </p><p>yuck .... autotools 🫤 </p><p>$ meson setup _builddir &amp;&amp; meson compile -C _builddir &amp;&amp; meson install -C _builddir </p><p>There. Fixed it for you.</p><p><a href="https://infosec.exchange/tags/meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson</span></a> <a href="https://infosec.exchange/tags/meson_buildsystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson_buildsystem</span></a></p>
Kevin Bowen :xfce:<p><span class="h-card" translate="no"><a href="https://mastodon.sdf.org/@jloc0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jloc0</span></a></span> </p><p>Indeed.</p><p>Aside from all of the other work going on, there is also a concerted effort to migrate from using <a href="https://fosstodon.org/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>autotools</span></a> to <a href="https://fosstodon.org/tags/meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson</span></a> for builds. </p><p><a href="https://fosstodon.org/tags/Xfce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Xfce</span></a></p>
TOV<p>GIMP 3.0’s development has improved significantly because the development team has switched from autotools to Meson for compiling. This has resulted in a major speed-up when building GIMP, allowing for quicker testing and development.</p><p><a href="https://mesonbuild.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">mesonbuild.com/</span><span class="invisible"></span></a></p><p><a href="https://fosstodon.org/tags/GIMP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GIMP</span></a> <a href="https://fosstodon.org/tags/Meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Meson</span></a> <a href="https://fosstodon.org/tags/build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>build</span></a></p>
Thomas Frans 🇺🇦<p>I love documentation like this. Straight to the point.</p><p><a href="https://fosstodon.org/tags/Meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Meson</span></a> <a href="https://fosstodon.org/tags/c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>c</span></a> <a href="https://fosstodon.org/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://fosstodon.org/tags/development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>development</span></a></p>
Erik C. Thauvin<p>Git 2.48 Released With Initial Support For The Meson Build System</p><p><a href="https://mastodon.social/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>git</span></a> <a href="https://mastodon.social/tags/meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson</span></a></p><p><a href="https://www.phoronix.com/news/Git-2.48-Released?utm_medium=erik.in&amp;utm_source=mastodon" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">phoronix.com/news/Git-2.48-Rel</span><span class="invisible">eased?utm_medium=erik.in&amp;utm_source=mastodon</span></a></p>
Helsinki Python<p>🎄 Christmas is nearly here and that means it's time to join us for our December meet, hosted by <a href="https://fosstodon.org/tags/Nitor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Nitor</span></a>!</p><p><a href="https://www.meetup.com/helpy-meetups/events/304793959/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">meetup.com/helpy-meetups/event</span><span class="invisible">s/304793959/</span></a></p><p>❄️ Creating Python modules and libraries using <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Rust</span></a>, by Akseli Lukkarila</p><p>❄️ <a href="https://fosstodon.org/tags/Meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Meson</span></a>: a Build system in and for Python, by Jussi Pakkanen</p><p>❄️ <a href="https://fosstodon.org/tags/JAX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JAX</span></a>: A Python ecosystem for machine learning and numerical computation, by Nazaal Ibrahim <span class="h-card" translate="no"><a href="https://sigmoid.social/@nazaal" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nazaal</span></a></span> </p><p>❄️ And did someone say something about a quiz?</p><p><a href="https://fosstodon.org/tags/HelPy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HelPy</span></a> <a href="https://fosstodon.org/tags/Helsinki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Helsinki</span></a> <a href="https://fosstodon.org/tags/Finland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Finland</span></a> <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> <a href="https://fosstodon.org/tags/meetup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meetup</span></a></p>
mgorny-nyan (he) :autism:🙀🚂🐧<p>I suppose I could use my experience to give some <a href="https://social.treehouse.systems/tags/PEP517" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PEP517</span></a> build system recommendations.</p><p>For pure <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a> packages:</p><p>1. <a href="https://social.treehouse.systems/tags/flit_core" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>flit_core</span></a> (<a href="https://pypi.org/project/flit-core/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">pypi.org/project/flit-core/</span><span class="invisible"></span></a>) — it's lightweight and simple, and has no dependencies (in modern Python versions, for older Pythons it vendors tomli).</p><p>2. <a href="https://social.treehouse.systems/tags/hatchling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hatchling</span></a> (<a href="https://pypi.org/project/hatchling/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">pypi.org/project/hatchling/</span><span class="invisible"></span></a>) — it's popular and quite powerful, but has many vendored dependencies and no stand-alone test suite (which makes it painful to maintain in <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gentoo</span></a>).</p><p>For Python packages with C extensions: <a href="https://social.treehouse.systems/tags/meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson</span></a>-python (<a href="https://pypi.org/project/meson-python/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">pypi.org/project/meson-python/</span><span class="invisible"></span></a>) — which combines the power and correctness of meson build system with good very Python integration.</p><p>For Python packages with Rust extensions: <a href="https://social.treehouse.systems/tags/maturin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>maturin</span></a> (<a href="https://pypi.org/project/maturin/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">pypi.org/project/maturin/</span><span class="invisible"></span></a>) — which is simply a good builder for precisely that kind of packages.</p><p>Now, I strongly discourage:</p><p>A. <a href="https://social.treehouse.systems/tags/setuptools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>setuptools</span></a> — lots of vendored NIH dependencies (that can alternatively be unvendored for cyclic deps), lots of deprecations over time (we're still seeing tons of deprecation warnings all over the place), many unsolved bugs (e.g. parallel C extension builds are broken in a few ways), a lot of technical debt, and if all that wasn't enough, it's slow.</p><p>B. <a href="https://social.treehouse.systems/tags/poetry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>poetry</span></a>-core — a very tricky build system with lots of pitfalls (I've reported a lot of mistakes done when migrating to it).</p><p>C. Practically any other build system — writing new backends is trivial, so everyone and their grandmother must have one. And then, they often carry a lot of NIH dependencies (if you're reinventing a build system, you may reinvent everything else), lack experience and reintroduce the same bugs. And if that wasn't enough, packaging them in distributions is a lot of work for no real benefit to anyone.</p>
Thomas Adam<p><a href="https://bsd.network/tags/fvwm3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fvwm3</span></a> <a href="https://bsd.network/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>autotools</span></a> <a href="https://bsd.network/tags/meson" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>meson</span></a> <a href="https://bsd.network/tags/muon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>muon</span></a> <a href="https://bsd.network/tags/buildsystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>buildsystem</span></a> </p><p>Hey all! Please note that although fvwm3-1.1.1 is close to being relesaed, there's still a few more things left to do.</p><p>Before that point, I'd like to take the opportunity to mention that as of fvwm3-1.1.1 fvwm3 is officially using meson/muon as the buildsystem of choice.</p><p>Autotools has been a tremendous help over the years. Heck, fvwm as a project started long before autotools existed.</p><p>But as technology changes, newer buildsystem alternatives have come along making better use of hardware, compilation speeds, etc.</p><p>Indeed, because of fvwm's age -- there's a tonne of custom m4 macros -- some of which are to work around issues long since gone. With autotools recently deprecating many of these, maintaining this was becoming difficult. Hence the change.</p><p>A six-month window exists once fvwm3-1.1.1 is released for downstream packagers to make the move from autotools to meson.</p><p>The `main` branch in the fvwm3 repository contains both buildsystems. Please give meson some testing!</p><p>A huge thanks goes to Kanjie (Matt Jolly) -- without whom none of this work would have been possible. Thanks, Matt!</p><p>For more specific details. please see: <a href="https://github.com/fvwmorg/fvwm3/discussions/1068" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/fvwmorg/fvwm3/discu</span><span class="invisible">ssions/1068</span></a></p><p>Questions? I'm here...</p>