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

[Zachary Lund]

On Mon, 2013-04-01 at 17:00 -0500, Mark A. Flacy wrote:

> 

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

> 

> >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. 

> >

> >_______________________________________________

> >Scons-users mailing list

> >Scons-users at scons.org

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

> 

> Perhaps an example of what you really want to do that isn't supported easily by scons would help.  Namely, how does having a template file solve your problem?

> 


Herm... good question :D

I suppose ultimately, I'm having issues adding things like "#include"
statements (or anything that isn't directly support in Scons) in my
config header (i.e. outside of macros is the use of "typedef". If a
certain type doesn't exist, create an alternative). I suppose I could do
this using substfile like stated above... it just seems kinda round
about and sloppy. 

It's static content so I feel like substfile is overkill and/or overly
complicated for the task.