The modules in the trunk version are now 100% platform independent across all cameras and firmware versions....Any comments, questions or suggestions?
Quote from: philmoz on 30 / November / 2012, 21:34:19The modules in the trunk version are now 100% platform independent across all cameras and firmware versions....Any comments, questions or suggestions?Yea - I have a comment. Thanks for doing this.My only question is whether there is anything that needs to be done to ensure it stays this way ? Or did they end up that way on their own so will likely stay that way ?
For example in the modified makefile I'm testing it bypasses loading the propset?.h file. So any attempt to use a propset value will generate a compile error.
Quote from: philmoz on 30 / November / 2012, 21:55:38For example in the modified makefile I'm testing it bypasses loading the propset?.h file. So any attempt to use a propset value will generate a compile error.The "right" way to do this would be to make a set of module safe includes, and not include anything else in module code. Currently, the modules include things like platform.h and stdlib.h which have platform dependent ifdefs in them.I'm somewhat wary of having the autobuild build modules only once without that sort of protection, it seems like this could lead to subtle errors which might go unnoticed for a long time.The other possible concern is merging outstanding branches. The remote capture stuff is mostly in the core, but it does touch dng a bit. I suspect that trying to merge the "move" will not have the desired effect, but it can probably be resolved manually without a huge amount of pain. I don't know about tsvstars ui branch, it didn't start as a proper branch in the first place, and I don't know what if anything will go back to the trunk.
Any comments, questions or suggestions?
Quote from: philmoz on 30 / November / 2012, 21:34:19Any comments, questions or suggestions?Not related directly, but it would be nice if new modules could be added in a way that doesn't require modifying CHDK source. Maybe one subdir for a module somewhere in the source tree.
Not sure what you mean here.I'm trying to consolidate all the module code into one directory.As far as modifying CHDK for a new module you have to at least:- add it to the makefile- add it to a menu if it has a UI you want to invoke- add code to ubasic, lua or other core routines to call the module- potentially update the loader to handle load/unload of the moduleI doubt it would be possible to get around most of this.There was an experiment in dynamically building a module menu at startup; but it was not stable on all cameras and would also cause problems with the current 'user' menu implementation.
Started by NewbieToobie General Discussion and Assistance
Started by quid « 1 2 » General Discussion and Assistance
Started by ehowland General Discussion and Assistance
Started by zell « 1 2 » General Discussion and Assistance
Started by reyalp General Discussion and Assistance