<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#C0C0C0" bgcolor="#330000">
Hi again, Peter<br>
<br>
<div class="moz-cite-prefix">Em 06/10/2021 17:18, Peter Richards
escreveu:<br>
</div>
<blockquote type="cite"
cite="mid:20211007071807.36fac87d@Dell-Inspiron-3542">
<pre wrap="">Hi Dedeco,
On Wed, 6 Oct 2021 13:01:59 -0300
Dedeco Balaco via Users <a class="moz-txt-link-rfc2396E" href="mailto:users@lists.claws-mail.org"><users@lists.claws-mail.org></a> wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Anyway, can I compile it and then install it ?? Looked at
<a class="moz-txt-link-freetext" href="https://lists.claws-mail.org/pipermail/users/2021-September/028752.html">https://lists.claws-mail.org/pipermail/users/2021-September/028752.html</a>
, so will read through that and see if it makes sense.
</pre>
</blockquote>
<pre wrap="">
Yes. The most you will need to do is to install some development
packages that are needed to compile the source. Else, compiling it is
fairly simple. I learned it in the last weeks.
</pre>
</blockquote>
<pre wrap="">
I noticed that you raised the initial question in that thread. Did you
find a complete/definitive set of instructions on how to compile a
plugin please ? I have browsed through that thread on the lists, but
the information seemed not complete ??
</pre>
</blockquote>
<p>I discovered that we can compile just Claws plugins (or a single
specific one, recently). And we can also compile a full Claws Mail
to live completely separated from the one we get by installing the
distribution package, with synaptic, aptitude or apt* and dpkg
family of commands, using the right repositories.<br>
</p>
<p>I do not remember the exact answer, or the name of who said to me
"to compile and install just the plugin, do A, B, C". Use your
mail manager to show this list messages in thread format, and
check the few threads i fairly recently started. It was much
easier than i imagined possible.</p>
<p>Have you ever, before compiling any source, configured the
project to install in a different place, and use everything
relative of that place, including user configuration files? You
will pass some arguments to the "./configure" command that people
said to you here. But execute it alone! Do <b>*not*</b> call
other commands in the same line using "&&" after it. Do
each thing separatedly. I prefer like that.</p>
<p>"./configure --help" command helps a lot, sometimes.<br>
</p>
<p>And if you really want to try everything just to test, about
Claws, install the packages needed to compile, get the complete
Claws Source, unpack it to a new directory inside /dev/shm</p>
<p>This folder lives in RAM! So, everything will be lost if your
computer turns off. But basically nothing will be written to your
disk, protecting its life a little bit. If you compile with the
right flags, everything can happen just inside RAM folders. I love
this!<br>
</p>
<p>😁👍🏾<br>
</p>
</body>
</html>