new branch - CHDK : Elf Edition - Developers wanted - page 6 - General Discussion and Assistance - CHDK Forum supplierdeeply

new branch - CHDK : Elf Edition - Developers wanted

  • 316 Replies
  • 110553 Views
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #50 on: 12 / December / 2011, 08:34:13 »
Advertisements
To invoke the modules, a menu with the available modules would be user-friendly.

Currently most modules could be called as before from main menu. File selector is used just for direct call modules.
I do agree that it could be integrated as user-friendly list. I have an idea how to do that. But just have no time to implement it right now. It will require some changes in convertor to simplify including information about module. And surely increase complexity of modules. Because we need to describe information and flags (like "do not show in modulelist" for libraries and specific modules)
« Last Edit: 12 / December / 2011, 08:37:07 by tsvstar »

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #51 on: 12 / December / 2011, 09:21:19 »
@ all devs
Great stuff, this should kick CHDK into (memory management) adulthood !
I can also see great potential for reducing the number of compile time options.

Got 1477 to compile with GCC 4.6.2, but ONLY if I changed (in core/modules/Makefile, line 17)
Quote
// this fails with "arm-elf-gcc.exe: error: missing argument to '-d'"
LDOPTS+=-Wl,-N,-Ttext,$(MEMISOSTART) -r -d
// this works
LDOPTS+=-Wl,-N,-Ttext,$(MEMISOSTART) -r -Wl,-d

... Both cameras (A720, SX220) work with this version without any problems. I can call the modules (not all tested). The module inspector works. To invoke the modules, a menu with the available modules would be user-friendly.

msl
Same here for ixus220_elph300hs - about the module inspector: it has a small visual bug, after leaving
it by pressing 'Menu' the info is not cleared until the Debug menu is left  (with 'Back')
Tried versions compiled with GCC 4.6.2 as well.

cheers,

wim


Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #52 on: 12 / December / 2011, 12:23:26 »
Works are moved into reyalp-flt branch.

What is changed:
- Added CHDK/MODULES dir
- Fix for GCC4.6.2 (from whim)
- Changing root Makefile to keep compiled modules in CHDK/MODULES (from philmoz)

Changes for optionally compilation important parts as modules are ready but not committed yet. They are slightly increase _visual_ complexity of this modules.
Simple one common option OPT_GENERIC_MODULES is used to control that.  Works stable in both variants.

I will commit to branch this tomorrow if no objection.

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #53 on: 12 / December / 2011, 13:46:08 »
... What is changed:
- Added CHDK/MODULES dir
...

Sorry, but just adding to source tree doesn't work (it must get wiped somewhere  ?)
What works for me is adding to root Makefile, after:
Quote
   mkdir -p  $(topdir)bin
add:
Quote
   mkdir -p  $(topdir)CHDK/MODULES

HTH,

wim


*

Offline reyalp

  • ******
  • 14035
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #54 on: 12 / December / 2011, 16:45:40 »
Changes for optionally compilation important parts as modules are ready but not committed yet. They are slightly increase _visual_ complexity of this modules.
Simple one common option OPT_GENERIC_MODULES is used to control that.  Works stable in both variants.
I'm not sure this is needed. My main reason for wanting to start with simple stuff was to minimize code changes. If we are changing all the code to support modules anyway, and then adding ifdefs on top of that, I'm not sure it's worth the effort.

I'd welcome others opinions on this.
Quote
I will commit to branch this tomorrow if no objection.
Please feel free to commit whatever you want in the branch.
Don't forget what the H stands for.

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #55 on: 12 / December / 2011, 16:57:35 »
Changes for optionally compilation important parts as modules are ready but not committed yet. They are slightly increase _visual_ complexity of this modules.
Simple one common option OPT_GENERIC_MODULES is used to control that.  Works stable in both variants.
I'm not sure this is needed. My main reason for wanting to start with simple stuff was to minimize code changes. If we are changing all the code to support modules anyway, and then adding ifdefs on top of that, I'm not sure it's worth the effort.

I'd welcome others opinions on this.

I don't think this is needed.

The CHDK/MODULES directory is included in both the small and full .zip files.
So long as you copy the entire .zip file to the SD card then everything should work as it does today.

For partitioned cards you would only need the modules on the small partition if the partition swapping isn't working for some reason - if it is then the modules will be loaded from the large partition.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #56 on: 13 / December / 2011, 00:44:42 »
I'm not sure this is needed. My main reason for wanting to start with simple stuff was to minimize code changes. If we are changing all the code to support modules anyway, and then adding ifdefs on top of that, I'm not sure it's worth the effort. I'd welcome others opinions on this.
I don't think this is needed.
The CHDK/MODULES directory is included in both the small and full .zip files.
So long as you copy the entire .zip file to the SD card then everything should work as it does today.

This is two reason why I do not commit this changes yet. I see small benefit with complexity increase (which is more valuable).
Surely any modules could be reverted to integrated state. As for me changes in each module are small and use same scheme. Modules are stable.
« Last Edit: 13 / December / 2011, 00:52:25 by tsvstar »

Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #57 on: 13 / December / 2011, 06:44:23 »
Flat modules branches updated:
- Extend module info
- Fix makeexport to correct generate #define CHDK_BUILD_NUM
- Fix modules/makefile (accidentaly had part of "optional generic modules" changes)
- Remove autocreated module_exportlist.h

Extending module information will allow to create isolated user-friendly module list.
But it make module format incompatible with previous version. Not big deal for now while module is not in production. :) Just make full compilation if you would like to try updated version.


*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #58 on: 13 / December / 2011, 10:33:11 »
@devs

Works reliably on my (ALPHA status) ixus220_elph300hs, but:

Compilation of a vanilla "reyalp-flt1483" still reliably fails for me under Windows,
(CHDK-Shell, using either GCC 4.5.1 or GCC 4.6.2) with:
Quote
cp: target `./CHDK/MODULES' is not a directory
gmake: *** [firsub] Error 1
Offending line (45) in the root Makefile 'firsub:' section:
Quote
   cp $(topdir)core/modules/*.flt $(topdir)CHDK/MODULES
and can be cured by inserting:
Quote
   mkdir -p  $(topdir)CHDK/MODULES
before module copying is started (either as mentioned in #53 or right before the 'cp' )

Also, note that a 'gmake PLATFORM=x PLATFORMSUB=y clean' does not appear to remove any .flt ,
which seems odd to me - isn't it supposed to remove all binaries and intermediates, except for
those in /bin and /tools ?

HTH,

wim

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: new branch - CHDK : Elf Edition - Developers wanted
« Reply #59 on: 13 / December / 2011, 16:42:43 »

Compilation of a vanilla "reyalp-flt1483" still reliably fails for me under Windows,
(CHDK-Shell, using either GCC 4.5.1 or GCC 4.6.2) with:
Quote
cp: target `./CHDK/MODULES' is not a directory
gmake: *** [firsub] Error 1
Offending line (45) in the root Makefile 'firsub:' section:
Quote
   cp $(topdir)core/modules/*.flt $(topdir)CHDK/MODULES
and can be cured by inserting:
Quote
   mkdir -p  $(topdir)CHDK/MODULES
before module copying is started (either as mentioned in #53 or right before the 'cp' )


It looks like the CHDK/MODULES directory is not included in the zip file that CHDK-Shell downloads for the branch, even though it is in SVN.

I presume this is because the directory is empty in SVN.

Probably the simplest solution would be to put a small 'readme.txt' file in the CHDK/MODULES directory in SVN.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

 

Related Topics