<p></p>
<p dir="auto">I tried following the meson instructions in the <code>README</code> (what read the instructions??) and it works!!! <g-emoji class="g-emoji" alias="rocket" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f680.png">🚀</g-emoji></p>
<p dir="auto">For me plugins configures, compiles and add-ons works!!! (only one that I use :-) with <code>./autogen.sh --prefix=/home/lex/geany-meson --with-geany-libdir=/home/lex/geany-meson/lib/x86_64-linux-gnu</code>.</p>
<p dir="auto"><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/eli-schwartz/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/eli-schwartz">@eli-schwartz</a> the <code>--with-geany-libdir</code> was introduced to geany-plugins autotools build by the Geany Debian package maintainer because it was supposedly the "standard" way of doing things there instead of using <code>--libdir</code>.</p>
<p dir="auto">But the statement in the Geany <code>README</code></p>
<pre><code>By default, meson will install Geany to `/usr/local`. A different
prefix can be selected at the initial command or via reconfiguration:

`meson --prefix /opt build` or `meson configure --prefix /opt build`

</code></pre>
<p dir="auto">is incomplete on Debian and derivates.  I suggest something like:</p>
<pre><code>By default, meson will install Geany to `/usr/local`. A different
prefix can be selected at the initial command or via reconfiguration:

`meson --prefix /opt build` or `meson configure --prefix /opt build`

Meson will use the distro's preferred library location 
(eg `$prefix/lib/x86_64-linux-gnu` on Debian) or `$prefix/lib`. 
 
Note, the Geany plugins autotools build assumes `$prefix/lib` so if your 
distro uses a different location geany plugins must be built with the 
`--with-geany-libdir=` set to the libdir used by the meson build.
</code></pre>
<p dir="auto">The Geany autotools build also seems to work after this PR is applied.</p>
<p dir="auto">So I'm ok with it.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/2761#issuecomment-1066224545">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ47GRCL3W6IVXEQS2DU72DWHANCNFSM4ZDZAFLA">unsubscribe</a>.<br />Triage notifications on the go with GitHub Mobile for <a href="https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675">iOS</a> or <a href="https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub">Android</a>.
<br />You are receiving this because you are subscribed to this thread.<img src="https://github.com/notifications/beacon/AAIOWJYVNBMUCIFC233GI73U72DWHA5CNFSM4ZDZAFLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH6GUXII.gif" height="1" width="1" alt="" /><span style="color: transparent; font-size: 0; display: none; visibility: hidden; overflow: hidden; opacity: 0; width: 0; height: 0; max-width: 0; max-height: 0; mso-hide: all">Message ID: <span><geany/geany/pull/2761/c1066224545</span><span>@</span><span>github</span><span>.</span><span>com></span></span></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/2761#issuecomment-1066224545",
"url": "https://github.com/geany/geany/pull/2761#issuecomment-1066224545",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>