So what next for CHDK-PT ?It seems to be an okay "free" disassembler that is also useful for porting CHDK files between different firmware version of the same cameras. In a format that the CHDK build and gcc compiler understands. Which is what I intended.
However, since its release,
philmoz has made the painful process of creating a stubs_entry_2.S file almost trivial. What used to take a newbie (like me at the time) weeks to figure out is now generated automatically as a stubs_entry.S file. Thank you philmoz !
The CHDK-PT functions that convert stubs_entry_2.S files between firmware versions are really not needed anymore (unless you are porting a really old camera).
I'm thinking about moving to a version 2. Get rid of the stubs conversion stuff - not needed. But beef up the function that converts address.txt files. This function has been the topic of almost 100% of the questions about CHDK-PT. I need to rethink what that does and how. In a perfect world I guess you could just point it at a boot.c, capt_seq.c and movie_rec.c file from one camera and it would make the same file for another camera. Or at least for another camera of the same type but different firmware version. Need to think about that - I think that its mostly just grinding string compare work.
Also, would it be good to stop using the current auto-it function that paint the text box and do something lower level that supports cut & paste ? Another thing I've wanted to do if the effort is worth something to people.
Other changes ? I'm not expecting to be buried with request here but its a good time to put up your hand if you have any ideas.
Thanks.
ww
