1.4 development planning thread - page 7 - General Discussion and Assistance - CHDK Forum

1.4 development planning thread

  • 195 Replies
  • 48607 Views
*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: 1.4 development planning thread
« Reply #60 on: 17 / January / 2015, 04:32:28 »
Advertisements
Two questions to the new module menu items:
1. Is it possible to make a language macro for the hard coded submenu entry 'EyFi config'?
2. Is the old calendar entry still necessary?

msl
CHDK-DE:  CHDK-DE links

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: 1.4 development planning thread
« Reply #61 on: 17 / January / 2015, 04:52:33 »
Two questions to the new module menu items:
1. Is it possible to make a language macro for the hard coded submenu entry 'EyFi config'?

Yes, the string comes from the module title which can be a language string. I'll update this in SVN soon.

Quote
2. Is the old calendar entry still necessary?

Technically no; but I'm still undecided whether to make the calendar a Tool so it appears in the Tools menu, or just leave it as the old menu entry.

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)

*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: 1.4 development planning thread
« Reply #62 on: 17 / January / 2015, 07:48:56 »
Thanks for the update.

I am not a friend of duplicate entries, which make the things cluttered.

The calendar is a tool without a photographic function*. Therefore the place in the tools menu is good enough.

*A useful feature for photographers would be e.g. a calculator for sunrise/sunset and the blue hour for a given latitude/longitude or GPS data. For that we had  already made a script with an in-built calendar. => http://trac.assembla.com/chdkde/browser/scripts/twilight/twilive.lua

msl
CHDK-DE:  CHDK-DE links

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: 1.4 development planning thread
« Reply #63 on: 17 / January / 2015, 18:00:11 »
Attached is a patch of changes to the current makefiles - this does not include the previous changes for TARGET_CAM, TARGET_FW and TARGET_PID, it's only cleanup/rework.

The changes are:
- split the top level makefile.inc file into pieces based on the type of rules/settings (arm_rules.inc, host_rules.inc, build_rules.inc)
- add new makefile_xxx.inc files for specific types of code (tools, modules, arm, etc), these include just the settings & rules needed for the type of target
- remove the SKIPxxx rules to turn off things not needed for a target (SKIPINTERWORK, SKIPPLATFORMCHECK, etc).
- add a set of shortcuts to simplify the rules (e.g. $(topdir)tools becomes $(tools), $(topdir)$(PLATFORM) becomes $(cam), $(topdir)$(PLATFORM)/sub/$(PLATFORMSUB) becomes $(camfw), etc).
- move various rules and settings up to the highest level of included makefile where possible
- simplify the rules to build the full and small zip files.

I've tested this on 64 bit Linux with the autobuild toolchain, OS/X 10.10.2 and Windows 8.1.
Tested individual camera builds for G12, G1X and SX40, as well as many of the batch targets.

Since the changes affect a lot of files I'd like to ask others to please before I put this in SVN.
Any other suggested improvements are also welcome.

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)


*

Offline srsa_4c

  • ******
  • 4426
Re: 1.4 development planning thread
« Reply #64 on: 17 / January / 2015, 18:57:08 »
Attached is a patch of changes to the current makefiles - this does not include the previous changes for TARGET_CAM, TARGET_FW and TARGET_PID, it's only cleanup/rework.
Batch build on 32bit Linux is OK (4.6.4 arm-elf toolchain), resulting binary runs on a3200.

I don't yet know how this will affect my DIGIC 6 stuff...

*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: 1.4 development planning thread
« Reply #65 on: 17 / January / 2015, 19:29:08 »
I don't yet know how this will affect my DIGIC 6 stuff...

I'm hoping that simplifying the makefiles will make it easier to support Digic6; but I haven't looked closely at your changes yet.

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: 1.4 development planning thread
« Reply #66 on: 17 / January / 2015, 19:36:32 »
Builds fine on 64 bit Linux using hacki's autobuild stuff ( GCC 4.4.3 ). 

Did a complete trunk build and tested (a bit) on my S100.  All okay.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline msl

  • *****
  • 1276
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: 1.4 development planning thread
« Reply #67 on: 18 / January / 2015, 08:14:54 »
Attached is a patch of changes to the current makefiles ...
Test CHDK-shell, gcc 4.8.3, single compiling A720, SX220

The CHDK-shell basically works with this patch. Only a warning alert is new.
Code: [Select]
This trunk version does not adapt its CFLAGS to the compiler version automatically ...If you ignore this warning, CHDK is compiled successfully.

msl
CHDK-DE:  CHDK-DE links


*

Offline philmoz

  • *****
  • 3332
    • Photos
Re: 1.4 development planning thread
« Reply #68 on: 18 / January / 2015, 15:55:49 »
Attached is a patch of changes to the current makefiles ...
Test CHDK-shell, gcc 4.8.3, single compiling A720, SX220

The CHDK-shell basically works with this patch. Only a warning alert is new.
Code: [Select]
This trunk version does not adapt its CFLAGS to the compiler version automatically ...If you ignore this warning, CHDK is compiled successfully.

msl

Had a quick look at the CHDK-shell source and this warning looks like it was meant to pick up issues back when GCC 4 support was added.

It can probably just be removed from the CHDK-shell code (delete lines 3777-3790).
This should still work correctly for 1.3 (and even 1.2 and 1.1).

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)

*

Offline reyalp

  • ******
  • 13391
Re: 1.4 development planning thread
« Reply #69 on: 18 / January / 2015, 20:52:33 »
Since the changes affect a lot of files I'd like to ask others to please before I put this in SVN.
Tried on win7/64 with the gcc 4.5.1 toolchain from chdkshell and the gcc 4.8 standalone, ubuntu x64 with gcc 4.3.2. Didn't notice any problems.

Checked that all the builds booted but didn't test extensively. Didn't look at the patch in great detail but it seems like a positive direction to me.
Don't forget what the H stands for.

 

Related Topics