> When you tell the software that the files will be located in /a/b (in
> this case by using -DCMAKE_INSTALL_PREFIX=/a/b) and then you install it
> into /g/h (by using DESTDIR=/g/h make install) then it does exactly
> what you told it.
This part should usually be fine.
> b) you do not need to
On Mon, 2020-11-16 at 15:45 +0100, Markus Elfring via evolution-hackers
wrote:
> It seems that this is not directly supported so far with the provided
> version.
Hi,
no, no, no, I do not think so.
When you tell the software that the files will be located in /a/b (in
this case by using
> I did not notice any limitation.
A build system configuration limitation was demonstrated by missing
a known header file which is available in another selected storage location.
>> I would like to reuse software components directly from a “staged”
>> (test) installation.
>
> Sure, then do
On Mon, 2020-11-16 at 14:52 +0100, Markus Elfring via evolution-hackers
wrote:
> I noticed specific limitations.
Hi,
I did not notice any limitation.
> I would like to reuse software components directly from a “staged”
> (test) installation.
Sure, then do configure it as such.
> https://www.gnu.org/prep/standards/html_node/DESTDIR.html
I have read the document section “7.2.4 DESTDIR: Support for Staged Installs”
once more.
> Hint: You misuse the DESTDIR variable.
I got obviously an other impression.
> Hence, there's nothing to be changed in the build process.
I
On Fri, 2020-11-13 at 22:03 +0100, Markus Elfring via evolution-hackers
wrote:
> > Make sure you provide precise commands to reproduce the problem.
>
> The provided build data show helpful information for the failure
> to include a special header file.
Hi,
pity you denied to do the
