<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Il 16/05/23 08:39, Ozan Türkyılmaz ha
scritto:<br>
</div>
<blockquote type="cite"
cite="mid:CA+da1or+x3cnEX=vL0s9DGGf8z4nbUJO+wsu=4jR_p7OXV7pPg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Giancarlo Dessì <<a
href="mailto:slack@giand.it" moz-do-not-send="true"
class="moz-txt-link-freetext">slack@giand.it</a>>, 16
May 2023 Sal, 00:04 tarihinde şunu yazdı:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><br>
I grabbed also *pdal*, the update is almost ready, but I'm
studying how <br>
to install automatically various optional dependencies if
detected: <br>
unlike gdal, pdal enables various plugins only if users set
explicitly <br>
respectives flags in cmake (DBUILD_PLUGIN_X=ON). Some
dependencies have <br>
no slackbuilds in SBo, so they have to be created next time.<br>
</blockquote>
<div><br>
</div>
<div>Usually Maintainers put shell variables which are set by
the builder. But you can check them <br>
</div>
<div>yourself inside the script using pkg-config or checking
the existence of a library .so file.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Ozan<br>
</div>
</div>
</div>
</blockquote>
<p>Yes, but I think that a switchable optional dependency through an
environment variable can be useful and notify it in README. Some
source check optional dependencies with cmake and enable them
automatically in the build if detected. This is done for example
by gdal: his source include a powerful autodetecting process so
the slackbuild does not require to set environment variables. <br>
</p>
<p>Other applications, like ffmpeg for example, do not check if an
optional dependency is installed, so their build require to enable
manually the feature by adding manually specific flags to cmake.
PDAL has a similar behavior: the build of plugins is disabled by
default in the source. If not considered that in a slackbuild, the
package will be installed with limited features, but in some cases
this is very important: tools like gdal or pdal are needed to
read/write geo/spatial datasets in formats not common. For
example, the IceBridge format is used only for data released by a
single subproject of NASA. PDAL is able to manage it but this
feature is not added by default.</p>
<p>I would implement the slackbuild to extend automatically the
features of the package if supported by the system. Users may
disable them if not required passing an environment variable
and/or not installing an optional dependency.<br>
</p>
<pre class="moz-signature" cols="72">--
*********************************************************
Giancarlo Dessì
<a class="moz-txt-link-freetext" href="https://www.giand.it">https://www.giand.it</a>
Slackware Linux... because it works!
********************************************************* </pre>
</body>
</html>