Basile STARYNKEVITCH writes:
> Andreas Schwab wrote:
>> Basile STARYNKEVITCH writes:
>>
>>
>>> Andreas Schwab wrote:
>>>
Perhaps gengtype should be modified to always treat the files in
gtyp-input.list relative to location of that file.
> I probably misunderstood yo
On Sun, Jul 5, 2009 at 8:26 AM, Basile
STARYNKEVITCH wrote:
> Ian Lance Taylor wrote:
>>
>> Basile STARYNKEVITCH writes:
>>
>>
>>>
>>> @: $(call write_entries_to_file,$(realpath $(GTFILES)),tmp-gi.list)
>>> $(SHELL) $(srcdir)/../move-if-change tmp-gi.list gtyp-input.list
>>> $(STAMP) s-gtyp-
Andreas Schwab wrote:
Basile STARYNKEVITCH writes:
Andreas Schwab wrote:
Perhaps gengtype should be modified to always treat the files in
gtyp-input.list relative to location of that file.
I probably misunderstood your sentence. I parsed "that file" as
referring to gengtype, b
Basile STARYNKEVITCH 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]
>
>
Andreas Schwab wrote:
Basile STARYNKEVITCH writes:
In plugin mode (for the few plugins using PLUGIN_REGISTER_GGC_ROOTS),
gengtype needs a file list. So a plugin build (in its own directory) would
want to run (in Makefile syntax)
$(GCCBUILD)/gcc/gengtype -p $(GCCSOURCE)/gcc
$(GCCBU
Basile STARYNKEVITCH writes:
> In plugin mode (for the few plugins using PLUGIN_REGISTER_GGC_ROOTS),
> gengtype needs a file list. So a plugin build (in its own directory) would
> want to run (in Makefile syntax)
> $(GCCBUILD)/gcc/gengtype -p $(GCCSOURCE)/gcc
> $(GCCBUILD)/gcc/gtype-input.list p
Ian Lance Taylor wrote:
Basile STARYNKEVITCH writes:
@: $(call write_entries_to_file,$(realpath $(GTFILES)),tmp-gi.list)
$(SHELL) $(srcdir)/../move-if-change tmp-gi.list gtyp-input.list
$(STAMP) s-gtyp-input
In general, one should try to avoid changing a user specified relat
Basile STARYNKEVITCH writes:
>@: $(call write_entries_to_file,$(realpath $(GTFILES)),tmp-gi.list)
>$(SHELL) $(srcdir)/../move-if-change tmp-gi.list gtyp-input.list
>$(STAMP) s-gtyp-input
In general, one should try to avoid changing a user specified relative
path to an absolute path.
* Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 03:51:00PM CEST:
>
> The patch below solves the issue, but the generated gtype-input.list
> contains too much empty blank lines. Any suggestions on how to solve
> this?
> +## compute the realpath of above GTFILES - keeping language tags as befo
Ralf Wildenhues wrote:
Hello Basile,
* Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 12:10:17PM CEST:
It would be much easier for plugins if gtyp-input.list contained
only absolute paths. In my case, (AMD64/Debian/Sid), it contains
only two relative filepaths: auto-host.h & options.h
Hello Basile,
* Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 12:10:17PM CEST:
> It would be much easier for plugins if gtyp-input.list contained
> only absolute paths. In my case, (AMD64/Debian/Sid), it contains
> only two relative filepaths: auto-host.h & options.h
Over here it contains on
Hello all,
gengtype how has a plugin mode (when invoked with -p as the first
program argument after gengtype).
It would be much easier for plugins if gtyp-input.list contained only
absolute paths. In my case, (AMD64/Debian/Sid), it contains only two
relative filepaths: auto-host.h & options.
12 matches
Mail list logo
