[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Embed extra search paths into Lua build?
- From: Coda Highland <chighland@...>
- Date: Sun, 12 Jul 2015 11:09:01 -0700
On Sun, Jul 12, 2015 at 8:53 AM, Christopher Tallman
> On Sat, Jul 11, 2015 at 2:39 PM, Roberto Ierusalimschy
> <email@example.com> wrote:
>>> It seems to me that this kind of thing is exactly the kind of thing that
>>> luaconf.h is there for; don't be afraid to hack it. It was never meant to
>>> be the canonical source of Universal Truth across all Lua builds
>>> everywhere. You want to build a custom configuration, so you have to
>>> customize the configuration.
>> Right. 'luaconf.h' is there to be edited for configuration (see its
>> If you want, you can make your changes at the end of the file, by
>> unedefining and then redefining what you need (see last comments
>> in 'luaconf.h').
>> -- Roberto
> Thank you for the help. I really appreciate the breadth of options. :)
> We have a build process that builds several Lua versions from source,
> so it was nice to think there might have been a way to update our
> build script and propagate the changes to each built version.
> I think as long as I document my changes to luaconf.h appropriately,
> everything will be fine; I'll just have to remember to make the same
> update to whatever Lua version comes next.
Consider creating a patch file that makes the changes to luaconf.h
from a clean Lua source tree, and apply it automatically. Then you
only have to worry about it if the patch fails, and that'll be a
visible failure in your build process.