Should parrot_config report separate inst_ and build variables?

[François Perrad]

2009/4/30 Patrick R. Michaud <pmichaud at pobox.com>:
> On Thu, Apr 30, 2009 at 12:27:01PM -0400, Will Coleda wrote:
>> On Thu, Apr 30, 2009 at 12:21 PM, Andy Dougherty <doughera at lafayette.edu> wrote:
>> > Is that the desired behavior?  Or, perhaps, should the installed version
>> > of parrot_config *know* that it's the installed version and simply report
>> > the inst_ version of variables?
>>
>> IMO, all the config keys should NOT have an install vs. a build
>> variant. This way a language can just call "parrot_config", and be
>> sure they're getting the right values.
>
> +2

I agree too.
When I added inst_libparrot_ldflags, I don't found the best solution.
Now, I think that both version (libparrot_ldflags &
inst_libparrot_ldflags) must be deleted.

If we considere only *nix platform,
LIBPARROT = @libparrot_ldflags@
could be replaced by
LIBPARROT = -L at build_dir@/@blib_dir@ -lparrot

and
LIBPARROT = @inst_libparrot_ldflags@
could be replaced by
LIBPARROT = -L at bin_dir@ -lparrot

When mixing various platform, it's more complex.

François.

>
> Pm
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
>