Windows GUI for trunk building - page 11 - General Discussion and Assistance - CHDK Forum supplierdeeply

Windows GUI for trunk building

  • 771 Replies
  • 253679 Views
*

Offline fe50

  • ******
  • 3139
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Windows GUI for trunk building
« Reply #100 on: 22 / September / 2008, 06:47:15 »
Advertisements
Hi wim,

thx for the update, 1.67 is purring like a kitty cat...

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #101 on: 22 / September / 2008, 08:43:00 »
@fe50
Thanks, I think controlling the conditional compiles might be next ...

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #102 on: 05 / October / 2008, 11:37:31 »
CHDK-Shell-v168.zip - 1.08MB

No controlling of the conditional compiles (yet), but

  • added camera properties (from camera.h) as tooltips for camera checkboxes
    (i find camera.h hard to read, this 'updates' the default values with the cam
    specific ones, think wondering 'wat was it again, propcase 1 or 2 ?' or
    'did that support multipartition ?' etc.)
     :D
  • updated card menu to CardTricks 1.40 level:
    - check card size before creating Udumper; reduced empty.dum size (thanks PhyrePhox !)
    - updated udumper + sources (uses brake's new encode.c now)

enjoy,

wim
« Last Edit: 05 / October / 2008, 20:38:35 by whim »

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #103 on: 06 / October / 2008, 08:46:54 »
bug fix edition CHDK-Shell-v169.zip - 1.09MB

  • resources in \CHDK-Shell were sometimes not the most recent versions  :-[
  • included comments in cam props tooltips  :)

wim


*

Offline reyalp

  • ******
  • 13831
Re: Windows GUI for trunk building
« Reply #104 on: 06 / October / 2008, 19:33:14 »
Whim: If it would be easier for you to have the conditional compile stuff controlled differently, just let me know. The current setup was just quick and dirty. For example, we could easily make a file (e.g. buildconf.inc) which only contains conditional compile options.
Don't forget what the H stands for.

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #105 on: 07 / October / 2008, 06:02:54 »
@reyalp

funny, I was just thinking about contacting you about that ! It's true, a conditional.inc
would make parsing and specially rewriting a bit easier. On the other hand, I would
still need to be able to find them in makefile.inc too (backward compatibility).
So actually, my preference would be to just add an 'end' marker.
I can then first scan for '# build time optional components' then collect all
lines starting with 'OPT_' or '#OPT_' in a temp file, then 'treat' that and write it
back. In the new scheme I could stop scanning at the end maker, and even use
the end marker to backfix old builds accordingly.
Plus, less work for you  :D


wim

 

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #106 on: 07 / October / 2008, 20:08:12 »
Ok, here's a first version with Conditional Compile control  [edit: link removed, bugfix in newer post]

@reyalp - no modifications were necessary, but it does depend on the options being
                 after '# build time optional components' and it expects this string to be
                 present ...

  • GUI control for conditional compile options (click cog wheel above compile buttons
    to show the button; it will be hidden if the selected build does not have options)
  • cam props tooltips now have their own on/off checkbox
  • info icon left of the current release version shows internal build number and gives
    access to the version history ('version.txt') if available
  • now keeps the secondary windows (Branch Config, GUI Config, etc) 'on top' so you
    don't 'lose' them with an accidental click.
  • updated card menu: checkbox added to add 'EOS_DEVELOP' flag to boot sector, useful
    if you need bootable CF disks for your Canon DSLR

enjoy,

wim
« Last Edit: 08 / October / 2008, 04:56:23 by whim »

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #107 on: 08 / October / 2008, 04:51:36 »
Oh no !!! not another bugfix !!!   [edit: removed due to newer bugfixed++ edition]

  • bugfix: due to a missing initialisation the card menu could falsely report the card
    as non-bootable until the CF checkbox or 'make bootable' had been used.
  • added an up to date readme.txt this time  :D

hope you guys (/girls ?) don't get too annoyed with me,

wim
« Last Edit: 08 / October / 2008, 11:19:15 by whim »


*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Windows GUI for trunk building
« Reply #108 on: 08 / October / 2008, 06:16:34 »
every change is progress :)
thanks whim

*

Offline whim

  • ******
  • 2044
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #109 on: 08 / October / 2008, 11:16:53 »
Guess what ?  CHDK-Shell-v172  [edit: link removed]

@PhyrePhox : mwah, not always; maybe this time ...  :D

  • bugfix: compilation failed when changing conditional compile option(s) (missing tab's  :-[)
  • added option to keep objdump (assembly) output on a per target base - will be stored
    as 'bin\logs\dump-[cam]-[firm].txt' (attention: 3+ Mb per cam/firm)

wim

[ed: at least i squash'em before they get reported  ;))
« Last Edit: 20 / October / 2008, 03:12:21 by whim »

 

Related Topics