#649: Should parrot_config report separate inst_ and build variables?
----------------------+-----------------------------------------------------
Reporter: doughera | Owner:
Type: RFC | Status: new
Priority: normal | Milestone: 1.4
Component: install | Version: 1.1.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by doughera):
One way I was imagining this might be implemented is to indeed have
Configure.pl generate two versions of each of the relevant variables, e.g.
{{{ libparrot_linkflags}}} and {{{ inst_libparrot_linkflags }}}, to pick
an example from TT #698. In the build directory, parrot_config would
contain both of these, but the normal usage, namely {{{
libparrot_linkflags}}} would pick up the build directory version. Upon
building the parrot_config for installation, however, every inst_*
variable would be copied to it's corresponding non-inst_ variable
(e.g. inst_libparrot_linkflags would be copied to libparrot_linkflags) so
that in the installed version, you would also simply use {{{
libparrot_linkflags}}}. That is, users of parrot's config information
would use the same interface regardless.
The change would also be rather mechanical -- each inst_ variable has a
corresponding version without the inst_ prefix. The inst_ variables could
all be set up in Configure.pl right after the plain versions were set.
Unfortunately, the installed vs. not-installed information is currently
spread out in diverse ways across many files. Various build tools have
--install flags that do various things. Ideally, in the end, all they
would do is pick out which parrot_config file to load in, and much of the
remaining conditional code could be eliminated.
At least that's how I've been thinking it might look going forward.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/649#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
