Change prefix in gpgconf
Gatis.Paeglis at theqtcompany.com
Wed Nov 11 13:38:00 CET 2015
> There should never be a need for a user to weak this after installation.
There is a need for tweaking a prefix quite frequently, especially in cross compilation environments. I don't know the details on how this works in yocto,
but the general idea is that you export new environment that defines a new root for a sysroot, for example:
where cortexa9hf-vfp-neon-poky-linux-gnueabi has the standard paths, like /usr/ /bin/.
It should be possible to install the generated toolchain in any path, or even several paths at the same time. And later all operations (looking for include headers, linking libraries)
happen in the SDKTARGETSYSROOT.
Does this clarify why gpgconf is inflexible for this use case?
From: Werner Koch <wk at gnupg.org>
Sent: Wednesday, November 11, 2015 8:45 AM
To: Paeglis Gatis
Cc: gnupg-devel at gnupg.org
Subject: Re: Change prefix in gpgconf
On Tue, 10 Nov 2015 20:27, Gatis.Paeglis at theqtcompany.com said:
> After looking at the code it seems like there is no way to change paths in gpgconf after it has been build. Is this correct?
Right, it is a common Unix thing to hardwire certain locations so to
glue things together. There should never be a need for a user to weak
this after installation. Use appropriate configure and make options
Why do you want this?
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gnupg-devel