Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


On 30/09/2018 15:04, Maarten Hoes wrote:
So, my futile attempt was :

./bin/gbuild-to-ide --ide vim --make make


Which resulted in this:

Traceback (most recent call last):
   File "./bin/gbuild-to-ide", line 1664, in <module>
     gbuildparser = GbuildParser(args.makecmd).parse()
   File "./bin/gbuild-to-ide", line 83, in __init__
     self.binpath = os.path.dirname(os.environ['GPERF']) # woha, this is
quite a hack
   File "/usr/lib64/python3.6/os.py", line 669, in __getitem__
     raise KeyError(key) from None
KeyError: 'GPERF'


Appearantly, 'gbuild-to-ide' assumes some environment variables are set
(GPERF, SRCDIR, BUILDDIR, INSTDIR, and WORKDIR), but I cannot determine what
would be sane/expected values for these variables. Okay,
SRCDIR/BUILDDIR/INSTDIR seem self-explanatory (but you know what happens
when we assUme), but what are WORKDIR and GPERF ?

That smells like gbuild-to-ide needs to be run from within gbuild's "config_host.mk polluted" environment, which can be done via the "cmd" make target, i.e., something like

  make cmd cmd='bin/gbuild-to-ide --ide vim --make make'

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.