#662: [PATCH] Add more dependencies on parrot.h
----------------------+-----------------------------------------------------
Reporter: doughera | Owner:
Type: patch | Status: new
Priority: normal | Milestone:
Component: none | Version: 1.1.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by doughera):
Replying to [comment:1 jkeenan]:
> At what point in the build process would someone run `gcc -MM`?
I suppose that *after* a full 'make' is probably most sensible. That way,
all the auto-generated C files will have been generated. (Or at least all
those appropriate for your platform.) I can't think of a simple one-line
command to get them all because Parrot's build structure spans several
directories, some of which have their own separate Makefile, and some of
which don't. Still, something vaguely like this (off the top of my head,
completely untested, quite possibly completely wrong) might work on Unix:
{{{
for f in `find src compilers/imcc -name '*.c' -print | sort`; do
target=`echo $f | sed -e 's!\.c$!$(O)!'`
gcc -Iinclude -MM -MT $target $f
done | sed -e 's!include/parrot!$(INC_DIR)!g' >>
config/gen/makefiles/root.in
}}}
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/662#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
