[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[fluid-dev] Again on "Compile time constant lookup tables"
From: |
Carlo Bramini |
Subject: |
[fluid-dev] Again on "Compile time constant lookup tables" |
Date: |
Sun, 16 Sep 2018 11:09:52 +0200 (CEST) |
Hello friends,
I was wondering what you think about using an external tool for compiling the
const tables, like Python. Few lines on code into the CMakeLists.txt, no extra
options, no compile time macros. After creating those tables, the compilation
of the C code will work on all C compilers of the world. The tool will be
searched by cmake with REQUIRED option. If we would like to avoid that, we may
add a test for testing the presence of the generated files inside a specific
directory, but perhaps it is not worth to do that extra work: in my opinion,
having Python (or something else if you want) just at compile time is much less
restrictive than having GLIB dependency at runtime.
what do you think?
Sincerely.
- [fluid-dev] Again on "Compile time constant lookup tables",
Carlo Bramini <=
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Marcus Weseloh, 2018/09/16
- Re: [fluid-dev] ?==?utf-8?q? Again on "Compile time constant lookup tables", Ralf Mattes, 2018/09/16
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Tom M., 2018/09/17
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Marcus Weseloh, 2018/09/17
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Tom M., 2018/09/18
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Carlo Bramini, 2018/09/18
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Marcus Weseloh, 2018/09/18
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Marcus Weseloh, 2018/09/18
- Re: [fluid-dev] Again on "Compile time constant lookup tables", Tom M., 2018/09/20