[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Determination of default configuration values for build projects and
From: |
SF Markus Elfring |
Subject: |
Re: Determination of default configuration values for build projects and checking the settings |
Date: |
Tue, 11 Jul 2017 19:19:45 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
>> How would you handle data format conversions for providers of configuration
>> information?
>>
>> Would you like to care for transition phases until a general agreement
>> could be achieved for blessed values by involved contributors for the
>> affected software area?
>
> Could you back up a bit and tell us the original problem you are
> trying to solve, please?
Yes. - I am trying to convert a few build scripts from another
evolving free software to an Automake based approach.
See also:
Support for out-of-source builds by make scripts
https://github.com/ocaml/ocamlbuild/issues/245
> What you are saying does not make very much sense.
I assume then that a bit more concrete background information can help
in a better understanding.
The following command is used there.
https://github.com/ocaml/ocamlbuild/blob/81f849564672b75d90ac04713f614ed77b5bd7dc/configure.make#L9
…
include $(shell ocamlc -where)/Makefile.config
…
This specification can be resolved to another make script which contains
the information “# generated by ./configure …” in the first line.
So I became curious on how such data can be transformed into desired
default configuration values in similar use cases.
Regards,
Markus