Permalink
Browse files

Fix for parrot 5.0: clean MANIFEST.generated

  • Loading branch information...
1 parent f8568f1 commit 1c8be6f3f551953fc7709abb064c861c433d0150 Reini Urban committed Jan 7, 2013
Showing with 1 addition and 0 deletions.
  1. +1 −0 tools/build/Makefile.in
View
@@ -244,6 +244,7 @@ DOCS = README CREDITS LICENSE docs/*
CLEANUPS = \
*.manifest \
*.pdb \
+ MANIFEST.generated \
$(PERL6_PBC) \
$(PERL6_EXE) \
$(SETTING_PBC) \

5 comments on commit 1c8be6f

Rakudo doesn't have a MANIFEST.generated file, so it shouldn't be cleaning one up.

Pm

Owner

Parrot 5.0 creates a MANIFEST.generated file in Rakudo's build dir...? What step will do that?

Owner

All parrot steps which create installable files add these generated file to a new MANIFEST.generated file in builddir.
In the rakudo case this is currently not much, only the generated dynpmc header files, created by pmc2c.pl

$ cat MANIFEST.generated 
src/pmc/pmc_perl6lexinfo.h                       [devel]include
src/pmc/pmc_perl6lexpad.h                        [devel]include
src/pmc/pmc_mdthunk.h                            [devel]include
src/pmc/pmc_ctmthunk.h                           [devel]include
Owner

I'm thinking of removing these generated lines from pmc2c and move it over to the parrot Makefile. So that this 2nd patch can be avoided. See parrot/parrot#922

Please sign in to comment.