make install thoughts

[Leopold Toetsch]

We still have the problem to access runtime files with an installed
parrot. So what about this idea:

* we have another source file (parrot_config.c) that gets linked to parrot
* this source file has basically just one CONST_STRING holding the
frozen image of the parrot configuration (config.fpmc)
* at parrot startup this string is available as e.g.

interpinfo Sx, .INTERPINFO_PARROT_CONFIG
thaw Px, Sx # config hash

Noe building Parrot would look like:
* link against empty (dummy) or old parrot_config$(O)
* invoke parrot to create frozen config (config.fpmc)
* invoke a utililty that converts this file to C source (with some
hexified constants holding the frozen image string)
* if this new file differs from the old parrot_config.c:
* then recompie/relink with the new config settings (which is just the
normal Makefile rule if a file changed)

With that sequence we should have a Parrot executable that has all
config settings builtin.

Comments?
leo

[Jens Rieks]

On Tuesday 05 October 2004 13:22, Leopold Toetsch wrote:
> Comments?
What about using miniparrot to create parrot_config.c?

jens

[Leopold Toetsch]

Yep. Finally yes. But building miniparrot is another untested step in
that process. For now and the release using the regular parrot is ok.

> jens

leo