metadata generator / build process (Re: CHIMP)

@reyalp I managed to port the module metadata code to CHDK (to run as a module).

Question: How do I go about sharing code between tools and modules, e.g. meta_modules.c that needs to be built in both.

Generally speaking, one makefile would reference the .c file from the other directory. Host object or lib files should go in the tools directory. We currently have some cases that share includes (flt, lang and font related) but aside from hostlua and run-ubasic (which is probably broken) I can't think of anything offhand that shares actual code.

If it was shared with a module, I'd probably put the code used by both in the modules directory or under lib.

If it was shared with a module, I'd probably put the code used by both in the modules directory or under lib.

This is currently implemented as a module. So I just put the common code under modules and have the tools makefile build it into tools?

This is currently implemented as a module. So I just put the common code under modules and have the tools makefile build it into tools?

That's probably what I would do. If there are a lot of files involved, you might put them lib instead, like Lua.

I'm not clear on the reason to have this as a module.

I'm not clear on the reason to have this as a module.

The reason is it computes SHA-256 hashes of the modules and reads/writes JSON, which I believe to be too much for core.

Question: How do I go about sharing code between tools and modules, e.g. meta_modules.c that needs to be built in both.

Put the code in the 'modules' folder.
Create a new folder in the 'tools' directory for your meta_module tool, with it's own makefile (see elf2flt or packfi2 for example).
Add a custom build rule in the makefile, e.g.:

meta_module$(EXE): $(modules)/meta_module.c
   @echo $< \-\> $@
   $(HOSTCC) $(HOSTCFLAGS) -o $@ $^


Note, I have not tested the above so you make need to experiment with the build rule.


Phil.

Put the code in the 'modules' folder.
Create a new folder in the 'tools' directory for your meta_module tool, with it's own makefile (see elf2flt or packfi2 for example).
Add a custom build rule in the makefile, e.g.:

Code: [Select]


meta_module$(EXE): $(modules)/meta_module.c
   @echo $< \-\> $@
   $(HOSTCC) $(HOSTCFLAGS) -o $@ $^


Note, I have not tested the above so you make need to experiment with the build rule.


Phil.

Thanks, I'll try that.

Could you (or any of the moderators) please split this discussion starting from this post? It seems to have strayed pretty far away from CHIMP.

That worked perfectly. I now have both software metadata generator tool and menu metadata generator module using the same JSON writer!

I got the build tool to share some code with the flt tool.

For some reason, if meta_modules_get() from meta_modules.c is called from gen_meta_modules.c, it produces garbage output. In its current form, i.e. copied verbatim (with the name changed) to gen_meta_modules.c, it seems to work.

What am I missing? A buffer overrun perhaps?