Windows GUI for trunk building [currently v. 3.42]

[hwntw]

Un-comment the relevant lines in the top level Makefile, then restart CHDK-Shell. A430 will then appear in the camera models list.

[whim]

@ultima

But the "Branches .." button is greyed out (disabled) so I cannot get into the braches dialog

Since the available branches are determined by analysing the SVN source page, you must be connected
to do so, which means no branch configuration without connection.

sorry for late answer,

wim

[whim]

CHDK-Shell-v277 (update version)

• fixed:      most of the Z-ordering errors, I hope (the program popping over/under
                active app when performing checks)
  
  
• added:    message boxes with a timeout adapting to user (if you dismiss after 7 sec,
                next time it will use 7 sec timeout, etc. - the About/credits button in the
                Card menu is probably easiest to test this)
  
  

cheers,

wim

[whim]

CHDK-Shell-v278 (update version)

• added:   'Silent' option when checking both SVN sites; this suppresses site switching graphics
                and makes the program much more discrete (in 'Select SVN site' dialog)
  
  
• added:   Checking now also works when in the card menu, or when the main GUI is minimised
  
  
• added:   Splash popups (i.e 'Initialising ..' etc.) can now be switched off (in 'GUI..' dialog)
  
  
• fixed:     In 'Debug..' dialog:
               - Disabling Memory Garbage Collection was not saved to ini file
               - 'Apply' button now changes to 'Restart' when needed
               - Dialog button text now shows in red when profiling is active
  
  
• fixed:     In 'Cam Panel ..' dialog: controls for adjusting green component were hard to read,
               background colour now set to white
  
  

cheers,

wim

[whim]

======= WARNING FOR ALL USERS of CHDK-Shell =======

After receiving a report from ultimA (thanks!) and uploading CHDK-Shell-v278-sfx.exe
to the online virus scanning site jotti.org  4 out of it's 16 scanners are reporting that
the file is infected - the suspected file in the archive is 'CHDK-Shell\7za.exe'
'7za.exe' is a UPX compressed version of 7-zip 4.65 command line version which
I originally downloaded here: http://downloads.sourceforge.net/sevenzip/7za465.zip
The copy shipped with CHDK-Shell-v278-sfx.exe (after un-UPX-ing) only differs from the
original in that the checksums are not the same; filesize, timestamps, file property strings
are all the same.
 
So, for the moment:
         1)  I've taken down all CHDK-Shell versions from drop.io
         2)  I would advise anybody who installed v278 to perform a thorough scan for malware
         3)  Users of previous versions, please at least check the 'CHDK-Shell' folder for malware:
              in case of doubt replace '7za.exe' using the link above

Will post more info as soon as my full disk scan is done ...

Very sorry about this,

wim

[waldo]

VirusTotal reports that 10 of 41 virus checkers flag 7za.exe version 4.65 as malware.  Not entirely conclusive, but worrisome.

http://www.virustotal.com/file-scan/report.html?id=6f89e5d6235d1a44cf83f8a1d0da4cac6363a707a688803858061ec873f57c7e-1286580105

Edit: I found a version 4.32 of 7za.exe on my PC for supporting another program.  Here is its VirusTotal scan (0 out of 43):
http://www.virustotal.com/file-scan/report.html?id=46fa896b25527a1d87b0a0819e9c2b89776c77e9cd25679d618056e604a6f7ee-1286581230

[whim]

@waldo
The original 7za.exe version 4.65 (link see reply #379) also gets a clean bill of health from virus total (0 / 43)

@all
In the meantime, i've restored the files on drop.io; 2 files needed to be repacked with a clean '7za.exe':
'CHDK-Shell-v278-sfx.exe' and 'CHDK-Shell-v273-sfx.exe'.
During experimentation I also uploaded countless versions to virustotal, and have come to the conclusion that
having UPX'ed executables within the 7-zip selfextractor increases the number of scanners that complain ...
As an example, the 2 refreshed versions (v273 & v278) still get flagged by 1/43 scanner ("Jiangmin");
an experimental sfx with a non-UPX'ed CHDK-Shell-v278.exe gets a clean bill (0/43).
I'll keep that in mind for future releases ...

By the way, the only way the infected/abnormal 7za.exe could have found it's way into your CHDK
directory is if you have run CHDK-Shell-v278-sfx.exe and chosen to overwrite; if you use the
semi-automatic update the 7za.exe in your CHDK dir will extract with the option 'never overwrite',
and could never overwrite itself anyway, because it is running ...

This, of course, also means that if you're in doubt, you can just manually download the 'clean'
CHDK-Shell-v278-sfx.exe (dated Oct 11, 2010) here, run it, point it to your CHDK folder and choose
to overwrite all.

Sorry for the stress & work caused, and please ask if anything is unclear,

wim

[Bernd R]

I install and update to chdk shell 278, download all from svn and i can sucessfully compile a SX200is

the result is then in f:\chdk\DE\trunk\trunk443\bin dir

But i want compile Ixus 1000 HS a alpha version is still here(from asm1989), but Ixus 1000 is not list in compile options, i also dont see ixus 1000 in the trunk\platform as a folder.Ixus 300 HS i see too not.
 
My idea is to compile ixus 1000 Version and set on the code that is execute during boot a AF led on or other LED command, so i can tell you on what sourceline the Ixus 1000 crash

so please tell me or add to chdk shell a ixus 1000

[whim]

Hi Bernd,

If you want to compile a cam that is not yet in the trunk you need:

1. to know on which trunk version the source is based (I'll assume here it is 900)
    (BTW if you already have the proper trunk installed, you can skip straight to 2. )
    then get that version, in CHDK-Shell do:
    - click "Set SVN Site ..."
    - select "Browse CHDK" (or CHDKDE, if that's where your trunk version is from)
    - that will take you to the Root page of SVN
    - now click "trunk" -> you're in Root/trunk. Top right of page find "View revision"
    - type 900 and <Enter>, you will now see your revision's source
    - at the bottom of the page, in the center it says: "Download in other formats"
    - just below this you have "Zip Archive", click to download
    - rename the zip archive from trunk-r900.zip to trunk900.zip
    - add it to the proper /archives directory (the one for CHDKDE is in /DE )
    - now click "Unzip Archive .." , browse to your zip and confirm
    - you should now be able to select trunk900 by clicking "Change"
    - click "Source code folder" to get to {somewhere}/trunk/trunk900
   
2. - the alpha or beta source code for the cam, which you need to copy over
      your existing trunk - this will typically add new folders with your cams' name
      in your existing /loader and /platform directories, and update several files in
      /include; there might be more too ...
      if you are lucky there's also an updated Makefile, if not you will need to edit
      it (CHDK-Shell reads the Makefile to determine which cams are supported)
     

Hope that is enough to get you started,

wim
     

[Bernd R]

thanks i get the alpha sources, and i can compile with chdsk shell now, and a buiild need always 2 minutes because there is a clean do.
Is it possible to disable the clean so only changed files are compiled so all get faster ?

I have disable for test full compile and elf objdump, but this do not speedup.my other settings are all default, and i have also try with OPT_FI2

this is my log output

>> Cleaning in tools
>> Cleaning in tools/packfi2
>> Cleaning in lib
>> Cleaning in lib/font
>> Cleaning in lib/math
>> Cleaning in lib/ubasic
>> Cleaning in lib/lang
>> Cleaning in lib/lua
>> Cleaning in lib/armutil
>> Cleaning in platform
>> Cleaning in platform/ixus1000_sd4500
>> Cleaning in platform/ixus1000_sd4500/sub
>> Cleaning in platform/ixus1000_sd4500/sub/100d
>> Cleaning in core
>> Cleaning in loader
>> Cleaning in loader/ixus1000_sd4500
>> Cleaning in loader/ixus1000_sd4500/resetcode
>> Cleaning in CHDK

[whim]

Hi Bernd,

In "Compile Options" you can select Skip GMAKE clean after compile, which might save 5 - 10 sec
To remove cleaning before compilation you can try to modify the root Makefile:

replace @lines 69 and 89

...
firzipsub: infoline clean firsub
...
firzipsubcomplete: infoline clean firsub

with

...
firzipsub: infoline firsub
...
firzipsubcomplete: infoline firsub

In a quick try this worked for me (reduced time to compile unchanged source from 115 to 30 sec)

wim

[Bernd R]

thanks for info.

I see a small problem in chdk shell.
all compiler options are store, and load correct when i start new.only the compiler version setting is not store.

I use GCC 3.4.6 because this compile faster.

a full build with gcc 4 need 2 minutes and with 3.4.6 it need only 1 min 15 sec

[whim]

@Bernd K

Confirmed, will be corrected in next version.  Will also add option to Skip pre-compile cleaning - if you
can confirm that it works.

thanks,

wim

[reyalp]

Confirmed, will be corrected in next version.  Will also add option to Skip pre-compile cleaning - if you
can confirm that it works.

In the current build system, this is not at all safe. If you compile a different camera, different options, or change some files you will get a very broken build.

[whim]

@reyalp

Thanks, I already had my doubts 

wim