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'
_______________________________________________
LibreOffice mailing list
LibreOffice@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/libreoffice
