Hi Fabio,
The Makefiles do appear to be working.
I'm using reload because form upload from a file doesn't work well without it.
The upload works, but nothing else after does. There was a workaround on this
(?) list a while back, which said to set reload on, and that fixes it, no doubt
at the expense of performance.
I'd rather not have reload set on, but without it, my web app stops running
after the upload.
Thanks,
Jeff
--- On Sun, 3/21/10, Fabio Mascarenhas <mascaren...@acm.org> wrote:
> From: Fabio Mascarenhas <mascaren...@acm.org>
> Subject: Re: [Kepler-Project] What's really needed for xavante/cgilua?
> To: "Kepler Project mailing list" <kepler-project@lists.luaforge.net>
> Date: Sunday, March 21, 2010, 11:01 PM
> On Sun, Mar 21, 2010 at 11:43 PM,
> Jeff Otterson <otter...@yahoo.com>
> wrote:
> > Hi,
> >
> > That really does not work so well for me.
> >
> > I am building in a cross-tools environment, and the
> result of my build is an image that is sent to the target
> hardware.
> >
> > Right now, I fetch from the tarballs on github and
> luaforge, and run make and "make install" with the
> TARGET_DIR specified.
>
> Well, LuaRocks can be used in a cross-compiling
> environment, you can
> set specific CC and CFLAGS so LuaRocks will use your
> x-tools. LuaRocks
> 2 installs modules in the standard Lua paths, so you do not
> need it in
> the target environment, and can use it as a make
> replacement.
>
> I can't guarantee that the Makefiles are in sync, I haven't
> payed
> attention to them in a while...
>
> > I guess I'll need to try the CVS cgilua, because when
> I switched today to copas 1.1.6, wsapi 1.3.2 and xavante
> 2.2.0 (from copas 1.1.5, wsapi 1.2, and xavante 2.1) it
> looks like there is a memory leak when I configured
> xavante's config.lua like this:
> >
> > 34 { -- cgiluahandler example
> > 35 match = {"%.lp$", "%.lp/.*$", "%.lua$",
> "%.lua/.*$" },
> > 36 with = xavante.cgiluahandler.makeHandler
> (webDir, {reload=true})
> > 37 },
>
> Why do you need reload? The launcher will reload individual
> scripts if
> they are changed, anyway. You are not supposed to use the
> reload
> parameter in production, but it should not leak memory
> anyway. I am
> going to look into it.
>
> > Jeff
> >
>
> --
> Fabio Mascarenhas
>
> _______________________________________________
> Kepler-Project mailing list
> Kepler-Project@lists.luaforge.net
> http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
> http://www.keplerproject.org/
>
_______________________________________________
Kepler-Project mailing list
Kepler-Project@lists.luaforge.net
http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project
http://www.keplerproject.org/
