On Monday, 4 January 2021 08:21:57 CET Friedrich W. H. Kossebau wrote:
> And the proposal is to use ".in".
>
> Pros:
I would support just consistently adding ".in" (which, in the case of
producing Config files for cmake, means foo.cmake.in).
[ade]
signature.asc
Description: This is a
On Monday, 4 January 2021 08:21:57 CET Friedrich W. H. Kossebau wrote:
> And the proposal is to use ".in".
>
> Pros:
I would support just consistently adding ".in" (which, in the case of
producing Config files for cmake, means foo.cmake.in).
[ade]
signature.asc
Description: This is a
On 04.01.21 08:21, Friedrich W. H. Kossebau wrote:
> Hi,
>
> [replies only to kde-devel@kde.org, please]
>
> tl;dr This is a proposal to standardize on the suffix ".in" for input/
> template files passed to cmake's configure_file() in KDE projects.
>
>
> When it comes to naming the files
Hi,
[replies only to kde-devel@kde.org, please]
tl;dr This is a proposal to standardize on the suffix ".in" for input/
template files passed to cmake's configure_file() in KDE projects.
When it comes to naming the files used as templates for build-time generation
of source/data files by
Hi,
[replies only to kde-de...@kde.org, please]
tl;dr This is a proposal to standardize on the suffix ".in" for input/
template files passed to cmake's configure_file() in KDE projects.
When it comes to naming the files used as templates for build-time generation
of source/data files by