what is your Lua script writing environment like?

reyalp

Now I remember that problem

Here's a version of the script that runs 'require' in the correct environment, based on the one msl posted above. Bonus, you can now use --modroot to specify that path these are loaded from, e.g.

lua emu.lua test.lua --modroot=d:/chdk/trunk/CHDK

instead of having to copy all your scripts under A/

Since there seems to be some interest in this, I'm thinking about checking it in under the hostlua directory.

note the --conf option was something I planned but apparently never implemented. The idea was that it would be a local lua file that can customize the emulated environment, so for example you could set the propset, model etc without changing the main file. Also, you could override emulator functions, for example, you could make get_bv96 return a specific series of BV values to test your script.

edit:
this is now checked in, see http://trac.assembla.com/chdk/browser/trunk/tools/hostlua/emu/emu.lua for the latest version.

emu.lua

13.07KB

waterwingz

reyalp
Here's a version of the script that runs 'require' in the correct environment, based on the one msl posted above. Bonus, you can now use --modroot to specify that path these are loaded from, e.g.

Close .. the filespec under Linux is case sensitive so lines 443 & 445 need to have ".lua" in lower case to find the files from the CHDK distro file stored in A/

        local f=loadfile(camera_module_root..'/SCRIPTS/'..mname..'.lua')
        if not f then
                f=loadfile(camera_module_root..'/LUALIB/'..mname..'.lua')
        end

I assume there must be a more elegant way to make this case independent?

Since there seems to be some interest in this, I'm thinking about checking it in under the hostlua directory.

Seems like a good idea to me - I keep updating the camera functions to track what I'm working on and then losing it when I get a new version (not a big deal - each version gets better).

Might make sense to put the script functions into another file and including it in emu.lua. That way you seperate the emulator part from the actual CHDK functions.

note the --conf option was something I planned but apparently never implemented. The idea was that it would be a local lua file that can customize the emulated environment, so for example you could set the propset, model etc without changing the main file. Also, you could override emulator functions, for example, you could make get_bv96 return a specific series of BV values to test your script.

You're teasing us ... I think that finishing things so its easy to run from Notepad++ (rudy..) or Geany (me?) might make this a lot more popular with the average CHDK user (sort of like CHDK-Shell brought CHDK compiling to so many ...)

reyalp

waterwingz
Close .. the filespec under Linux is case sensitive so lines 443 & 445 need to have ".lua" in lower case to find the files from the CHDK distro file stored in A/

Oops, I thought they were upper case in the CHDK directory. Fixed. (edit: in the trunk)

I assume there must be a more elegant way to make this case independent?

It's a little bit tricky. You'd have to list the directory and do a case insensitive comparison or something.

Might make sense to put the script functions into another file and including it in emu.lua. That way you seperate the emulator part from the actual CHDK functions.

Yes. This is complicated by the fact that the Lua package loading code is heavily butchered in the CHDK version of Lua, and this caries over to hostlua.

See the #if 0 stuff in lua/lib/loadlib.c

While we could theoretically make some of the #if 0 into #ifdef HOST_LUA, it might be worth restoring some of this in chdk proper. I think the original reason it was butchered is because required functions like strchr were not available, but many of these have been found since.

reyalp

I've updated the trunk emu.lua in changeset 2724

This splits camera_funcs into it's own file. I also implemented the conf option.

note camaera_funcs.lua is expected to be available on the Lua path. The simplest way to get this is to run the emulator script from the emu directory, but hostlua built after r2723 should honor the LUA_PATH environment variable.

Example
../lua emu.lua test.lua --modroot=d:/chdk/trunk/CHDK --conf=a540.lua

example a540.lua conf file

local camera_funcs=require'camera_funcs'
function camera_funcs.get_buildinfo()
	return {
		platform="a540",
		build_date="Apr  7 2013",
		build_number="1.2.0",
		build_time="16:03:05",
		version="CHDK",
		platsub="100b",
		build_revision="2684",
		platformid=12571,
		os="vxworks",
	}
end
function camera_funcs.get_propset()
    return 1
end

The whole thing is pretty quick n dirty, it could really use some proper structure...

outslider

Hello!

I am looking for an information about how to compile this hostlua. Since I usually don't work with compilers I have completely no idea how to even start. I suspect I need to svn-download the trunc/tools from assembla and then compile it? But how...

Is there any description somewhere on the wikia? Or if this is not the case - can anybody describe the process here? Then I could try this myself and write a simple how-to on wikia.

Thank you in advance!

System: Kubuntu 12.04. I can also use Win7 instead.

reyalp

outslider
I am looking for an information about how to compile this hostlua. Since I usually don't work with compilers I have completely no idea how to even start. I suspect I need to svn-download the trunc/tools from assembla and then compile it? But how...

You need a complete CHDK build environment. There should be instructions for that on the wiki, though on linux it isn't entirely trivial.

On windows, CHDKShell should give you everything you need. Use the command prompt button to get a shell.

After the build environment is set up, you should be able to just

cd tools/hostlua
make

whim

On windows, CHDKShell should give you everything you need. Use the command prompt button to get a shell.

After the build environment is set up, you should be able to just ...

Confirmed working on CHDK-Shell v3.44 with trunk 2724 (tested compiling only)

wim

msl

Thanks for the hostlua & emu.lua improvements.

Our notepad++ project runs fine. The splitting of the camera functions is not so good (for our project), but it works.

msl

reyalp

msl
The splitting of the camera functions is not so good (for our project), but it works.

What problems does it cause? Maybe we can make it better.

outslider

Thanks for your help, after make I got compiled *something* but I still have no idea how to use the hostlua... I mean what to run to run a script.

If there's any documentation you could give me a pointer to I would appreciate that. Mainly to avoid wasting your time with my questions😀

msl

reyalp
What problems does it cause? Maybe we can make it better.

It's not really a major issue. It is more an organizational problem. All emulation files should be in one folder. But it is necessary that the file camera_funcs.lua is in A\CHDK\LUALIB.

For our notepad++ project we have a project folder:

hostlua\
       A\CHDK\LUALIB\ <all CHDK relevant Lua libraries>
       bin\ 
              chdkptp.exe
              emu.lua
              hostlua.cmd
              lremote.lua
              lua.exe
              luac.exe

It would be nice if we could insert camera_funcs.lua into the bin folder. But this does not work.

msl

reyalp

msl
It would be nice if we could insert camera_funcs.lua into the bin folder. But this does not work.

It should be possible to do this, as long as you are using lua.exe built from the latest trunk (2723 or later) hostlua. In fact, the default lua path should include the executable directory, so I would expect it to work without changes. If for some reason it isn't, you should be able to set LUA_PATH in the environment before executing it lua.exe.

If you can't get it to work let me know what the error message is. The working directory of lua.exe may also be relevant.

reyalp

outslider
If there's any documentation you could give me a pointer to I would appreciate that. Mainly to avoid wasting your time with my questions😀

There's no documentation outside of this thread and the relevant scripts

1) hostlua is a version of the lua standalone interpreter which is configured like CHDK lua (numbers are ints, various other CHDK specific hacks). See http://www.lua.org/manual/5.1/manual.html#6 for information about the standalone interpreter
2) emu.lua is a lua script which provides many of the functions that CHDK provides, and has the ability run other lua scripts in this environment.
3) The idea is that you can test and debug some aspects of your script without loading it on the camera.

As described in the emu.lua file, you can execute it like this

lua.exe emu.lua <name of your chdk lua script>

If you want to provide menu variables (a, b c etc) to your script, you can put -a=<number> -b=<number> etc on the command line.

outslider

The problem is that I got no lua.exe executable. I got for example dancingbits.exe, finsig_dryos.exe, makelang.exe and so on, but no lua.exe...

CHDK from which I compile is current trunk (https://tools.assembla.com/svn/chdk/trunk).

Regards!

philmoz

outslider
The problem is that I got no lua.exe executable. I got for example dancingbits.exe, finsig_dryos.exe, makelang.exe and so on, but no lua.exe...

CHDK from which I compile is current trunk (https://tools.assembla.com/svn/chdk/trunk).

Regards!

cd tools/hostlua
make

Phil.

outslider

philmoz

outslider
The problem is that I got no lua.exe executable. I got for example dancingbits.exe, finsig_dryos.exe, makelang.exe and so on, but no lua.exe...

CHDK from which I compile is current trunk (https://tools.assembla.com/svn/chdk/trunk).

Regards!

cd tools/hostlua
make

Phil.

Thx - worked. I feel stupid...

rudi

Thank you reyalp for your good work!
I could now change the position of camera_funcs.lua width new lua.exe and LUA_PATH. Only the bitwise operations are missing. Is imath-library a better (easier) place instead emu.lua implementation?

msl

reyalp
It should be possible to do this, as long as you are using lua.exe built from the latest trunk (2723 or later) hostlua.

That was it. As rudi wrote, now is all fine. Thank you for your help.

msl

reyalp

rudi
Thank you reyalp for your good work!
I could now change the position of camera_funcs.lua width new lua.exe and LUA_PATH. Only the bitwise operations are missing. Is imath-library a better (easier) place instead emu.lua implementation?

I was thinking about moving this to it's own C file, which could be used for both CHDK and hostlua.

rudi

Here is an updated emu.lua for new #params. It was tested with parmtest.lua.
Not so good is the different start index from lua tables and #values. Lua table functions can't use for #values with table extension in script.

rudi

EDIT: delete emu.lua, see next post

« Previous Page Next Page »