Content-Type: multipart/alternative; boundary=00148530af26bb64e704748446d2
--00148530af26bb64e704748446d2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi;
I've been making small changes to the build system in Nagios -- nothing in
shipping code, just aligning Nagios with the more recent Autotools.
I've commented why in a blog ep (
http://tech.chickenandporn.com/2009/09/ ... utoheader/),
no reason to pad it here. I think both my readers skipped past
Nagios' config.h.in looks generated; perhaps at some point Nagios used a
generated config.h and later that file was added-to, and was no longer
generated. Perhaps it copied a config.h generated somewhere else. I don't
know.
To get back to a generated config.h, the additions can be split off to a
file included in that config.h I've made that change in a patch which I've
attached.
The changes in the patch are basically leveraging the changes I submitted
for the configure.in to generate a config.h.in, then include a
"config-added.h" which includes the additional stuff. There's no
code-changes necessary in shipping code because the generated config.h
includes the new split-off content. The patch only references
configure.inand (new) include/config-added.h
Autoheader is a step in the "autoreconf" process.
FYC
Allan
--=20
[email protected] "=E9=87=91=E9=B1=BC" http://linkedin.com/in/gold=
fish
http://tech.chickenandporn.com/tag/nagios/
http://wiki.nagios.org/index.php/LDAP-Configured_Nagios
--00148530af26bb64e704748446d2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hi;I've been making small changes to the build syst=
em in Nagios -- nothing in shipping code, just aligning Nagios with the mor=
e recent Autotools.I've commented why in a bl=
og ep (http://tech.chickenandporn.com/2009/09/ ... can-survi=
ve-autoheader/), no reason to pad it here. =C2=A0I think both my reader=
s skipped past
Nagios' config.h.in looks generated; perhaps at some point Nagios used a generated config.h=
and later that file was added-to, and was no longer generated. =C2=A0Perha=
ps it copied a config.h generated somewhere else. =C2=A0I don't know.
To get back to a generated config.h, the additions can =
be split off to a file included in that config.h =C2=A0I've made that c=
hange in a patch which I've attached.The chan=
ges in the patch are basically leveraging the changes I submitted for the configure.in to generate a config.h.in, then include a "config-added.h"=
; which includes the additional stuff. =C2=A0There's no code-changes ne=
cessary in shipping code because the generated config.h includes the new sp=
lit-off content. =C2=A0The patch only references configure.in and (new) include/config-added.h
Autoheader is a step in the "autoreconf" proc=
ess.FYCA=
llan--=C2=[email protected] =C2=A0"=E9=87=91=E9=B1=BC" http://linkedin.com/in/goldfish=
http://tech.chickena=
ndporn.com/tag/nagios/http://wiki.nagios.org/index.php/LDAP-Configured_Nag=
ios
--00148530af26bb64e704748446d2--
--00148530af26bb64f704748446d4
Content-Type: application/octet-stream; name="nagios-autoheader.patch"
Content-Disposition: attachment; filename="nagios-autoheader.patch"
Content-Transfer-En
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]