building nvmetcli in buildroot
Christoph Hellwig
hch at lst.de
Fri Nov 10 00:19:17 PST 2017
On Fri, Nov 10, 2017 at 08:43:05AM +0100, stephane gonauer wrote:
> Hi,
>
> I dug further into the question to better understand.
>
> >From my understanding the root cause lies in setuptools :
>
> - buildroot uses --prefix option to set the prefix to $(TARGET_DIR)
> - the setup.cfg from nvmetcli uses -install-script
> - When both options are present, install-script completely overrides
> --prefix and is considered as an absolute path.
>
> I tried to uses $(TARGET_DIR) inside setup.cfg but it is not evaluated
> when reaching setup.cfg (and it results in a path containing the
> TARGET_DIR and not its value).
>
> Unless someone knows how to better use setuptools, I don't see a
> solution inside nvmetcli tree
What do other python tools that install into sbin or similar use?
There must be all kinds of precedence for this..
More information about the Linux-nvme
mailing list