> I'd say that this patch looks more like someone's personal easter egg,
> or at least you missed to explain why you would recommend other people
> to use an install structure as you do as well, what the benefit is over
> the one that they already have, and how they are supposed to create it,
> preferably automatically I'd assume...
Right.
> Other than that it is already possible to install the tcc executable(s)
> in a custom separate location, for example like
>
> ./configure --tccdir=... --bindir=...
>
> which is supposed to set CONFIG_TCCDIR explicitly and thus override the
> run-time automatism under libtcc.c:98: #ifndef CONFIG_TCCDIR.
It does if you can run a shell script, yes. Still, that creates a static path,
and when did those become the norm?
> "As a general rule, your messages should start with a single line
Got it.
--Fred