* On 18 Oct 2012, David Laight wrote: > > You want a dependency against config.status.
Good, thanks. > Please don't make the build require python. > A lot of systems don't have it installed. > There are much easier ways to get bits of strings compiled into a .c file. > > 1) just echo '"'"text string"'"', > file > and then #include the file in the middle a the C initialser. > > 2) Arrange to pass -DTEXT="text strings" on the command line to cc. > This one requires tricky quoting to get right. > Probably using as: > #define STR(x) #x > char foo[] = STR(TEXT); > will work. We cannot predict the content of the strings, so these both require tricky quoting to get right -- and that doesn't even touch on the problem of unforeseen trigraphs in arbitrary text input to the compiler. That's why I made a byte array encoder. I'm trying to get away from (g)cc as a runtime dependency for reporting bugs; cf. http://dev.mutt.org/trac/ticket/3537 . I'm happy to trade that for python as a build requirement -- it will be a very rare build system that doesn't have python and can't add it. It's not needed for runtime. Does anyone else think this is problematic? I could redo it in C if it's a widespread concern. -- David Champion • d...@bikeshed.us
