Basile STARYNKEVITCH <bas...@starynkevitch.net> writes: > Andreas Schwab wrote: >> Perhaps gengtype should be modified to always treat the files in >> gtyp-input.list relative to location of that file. > If we did that, we could not run gengtype in plugin mode as easily as > [Makefile syntax inside our plugin tree] > > $(GCCBUILD)/gcc/build/gengtype -p $(GCCSOURCE)/gcc > $(GCCBUILD)/gcc/gtype-input.list plugin.c > > because then the plugin.c would be expected to be inside the > $(GCCBUILD)/gcc or $(GCCBUILD)/gcc/build/ directory, which it is not.
It wouldn't. Any additional file specified on the command line would still be found relative to the current directory. > Also, modifying gengtype that way (which is non trivial: I don't know how > to *portably* and *easily* determine dynamically the location of an > executable: many non-linux systams don't have /proc/self/exe) Why would you need the location of the executable? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
