[Scons-users] Scons using config.h.in

[Zachary Lund]

On Sun, 2013-03-31 at 17:15 +0200, Marc Joliet wrote:

> Am Sat, 30 Mar 2013 00:10:32 -0500

> schrieb Zachary Lund <admin at computerquip.com>:

> 

> > 

> > I cannot seem to be able to find a reasonable method of using an

> > "outside" config. In autoconf, it's popular to have a "config.h.in" or

> > similar to import static source. Autoconf automatically expects a .in

> > file while scons doesn't seem to want to allow anything of the sort with

> > ease. 

> > 

> > Any chance I'm missing something? If not, would such a feature be

> > allowed in Scons?

> 

> Since nobody else replied yet:

> 

> I don't really know much of anything about autoconf, and hence what exactly

> you're looking for, but maybe env.Substfile (see the scons man page) can do

> what you want?

> 

> HTH

> _______________________________________________

> Scons-users mailing list

> Scons-users at scons.org

> http://four.pairlist.net/mailman/listinfo/scons-users


Herm... I suppose the autoconf macro 'AC_CONFIG_HEADERS' functionality
is what I'm looking for. You specify a header and it automatically looks
for a corresponding '<header>.in' to use as a template. 

Scons cannot do anything in thie config header outside of macro
definitions and even then its limited. Allowing the use of a template
header by default would ease the pain of both moving from Autoconf to
Scons and using scons in general.