acinclude.m4.in or configure.in.in?

[Stephan Kulow]

Am Samstag 03 Januar 2004 11:20 schrieb Brad Hards:
> What determines whether a check is put into
> kde-common/admin/acinclude.m4.in or into an application directory as
> configure.in.in? I assumed that it was if a check was likely to be needed
> by more than one app, but I see checks that are basically kimgio dependent
> in acinclude.m4.in.
>
> The issue is that the checks in acinclude.m4.in are slowing down every
> configure run, and I plan to add another one. Is there any reason why it
> can't be moved into kdelibs/kimgio/configure.in.in?
That dates back when kimgio was a simple library and every app linking to 
kimgio needed to link to all dependencies too. These days it could be in
kimgio/configure.in.in indeed. But on the other side, only a very little 
portion could be, as the test only calls some graphic lib checks that could
be used by other configures and then does a very small check.

Greetings, Stephan

-- 
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini שלום Peoch
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Py'guapy 평화