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

Windows GUI for trunk building

  • 771 Replies
  • 311427 Views
*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #60 on: 04 / July / 2008, 03:15:56 »
Advertisements
Starting two weeks ago, my CHDK GCC Shell tries to connect with tools.assembla.com and, after a while, an error appears, stating that the site seems to be unavailable. I've upgraded today to version 1.36 (was 1.33), but the problem is still there. I've even shutdown the firewall and the antivirus (they were no problem before) but to no avail. I'm stuck with trunk version 416. I can reach with my browser assembla.com and in tools.assembla.com I can see more recent versions, so it's not my ISP forbidding access to that domain. Any ideas? Thank you.

The shell Pings assembla.com with a 2 sec time-out, and errors like you described if it does not answer within that period.
Also, other programs that use lots of bandwidth could provoke the assembla.com Ping time-out.
If you turn on AutoCheck it should automatically recover (as stated in the error message).

HTH,

wim

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #61 on: 02 / August / 2008, 13:35:41 »
A small update to add support for the new juciphox Makefile option "batch-zip-complete" (from release 461)
Sorry for the version number bump, this is caused by my local intermediate trial versions for support of
real versions, not ready for release yet, though  :(

chdk-shell-v140.zip - 1.01MB

wim

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #62 on: 03 / August / 2008, 19:00:34 »
Update 1.50 - REAL versions !

from the readme.txt:
Quote
- 1.50  Now supports REAL versions for all branches. Short explanation: as some of you might know,
        assembla Trac bumps the version for all branches & trunk to the same version, for instance,
        at this moment downloaded trunk and juciphox source zips both claim to be 262, while actually
        juciphox was last updated in 261... now fixed, update will skip the 'fake' juciphox 262, which
        is just a 'rebadged' 261.
        Other changes:
        - option added to check & update  trunk+all branches or only trunk+selected branch, press
          "Select Branch ..." to find it. Please note that some branches are empty, they are being
          checked but nothing is downloaded. 
        - replaced "Auto Hide while compiling" with "Minimize CmdLine Windows"

it's here: chdk-shell-v150.zip - 1.01MB

have fun,

wim

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Windows GUI for trunk building
« Reply #63 on: 04 / August / 2008, 07:47:02 »
thanks whim :)

small "bug": when unchecking "allow internet" the buttons with the links to the forum, wiki and timeline disappear.
when for example at work i'm behind a proxy i cannot download the sources automatically, i can however open a browser and visit these sites :)

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #64 on: 04 / August / 2008, 09:01:28 »
Thanks, Phox !
Wish more people would post suggestions for improvement ...
Since I was just wrapping up a version 1.51, I included your suggested 'bug'fix.

Quote
from readme.txt
- 1.51  Significantly faster for Trac checks triggered by AutoCheck - this was achieved by skipping
        new checks on branches that report empty zip files on first check.
        Replaced: "Minimize CmdLine Windows" by "Debug (show & pause Cmd Windows)", when activated
        cmd windows will not autoclose. This allows easier reading of the output at the expense of
        forcing you to manually close them (thanks, PhyrePhox !)
        Changed: 'complete' compile option (see notes for 1.40) now pops up on selection of a build
        that supports it, rather than at compile time; previous versions would make Auto Compile
        useless on juciphox 461+
        Changed: internet links are not disabled anymore when the program fails to connect to assembla
        Trac (thanks, PhyrePhox !)

here's the link:

chdk-shell-v151.zip - 1.01MB

wim

*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Windows GUI for trunk building
« Reply #65 on: 04 / August / 2008, 09:04:36 »
Hi wim,

thx for the real versions, works fine  :D

A stop / cancel possibility while compiling would be nice, perhaps  Opt("TrayIconHide", 0)  as default, so the tool can be paused or stopped from the taskbar icon...and i can use it "out of the box"  8)

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #66 on: 04 / August / 2008, 09:27:01 »
Hi fe50 !

It is IMHO not very usefull to cancel/abort compilation, it might mess up your source
(intermediate files .o not properly cleaned up). Or do you mean interrupting inbetween
2 cams or firmwares ?
Apart from that, compilation happens by running CMD processes, which can not easily
be influenced by the shell. With the brand new 1.51 (see previous post) however, you
can activate Debug option, this will show the CMD windows. Then try to stop compilation
with Control-C, that might work ...
I could be wrong, but AFAIK setting Opt("TrayIconHide", 0) will only allow you to pause/stop
the script, not the spawned CMD processes. Will check it out, though.

edit: No joy,  TrayIconHide, 0 doesn't stop CMD processes and ^C will not work reliably, either :(
       Since a single cam/firm compilation takes less than 20 sec (on my Turion 1.8 GHz) can't you
       first do a test 'Compile Selected' for say your own main cam only, before going for lengthy
       multi cam/firm compile sessions ?

wim
« Last Edit: 04 / August / 2008, 09:51:13 by whim »

*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Windows GUI for trunk building
« Reply #67 on: 04 / August / 2008, 09:48:05 »
Hi wim,

yes, i always set TrayIconHide to 0, so when paused with the tray icon AutoIt stops after a completely done cam/firmware compile job, the compilation (CMD) job itself is not aborted. You can also close a running CHDK-Shell by the task bar icon, then the CHDK-Shell exits, but a still running CMD job can do it's job (the last cam/fw) normal...
The CMD job will not be influenced by the pause / exit...

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #68 on: 04 / August / 2008, 10:40:53 »
@fe50:

OK, done  :D 

switchable, sticky TrayIcon option:

chdk-shell-v152.zip - 1.01MB

*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Windows GUI for trunk building
« Reply #69 on: 04 / August / 2008, 11:23:57 »
thx wim, works fine !

Quote
edit: No joy,  TrayIconHide, 0 doesn't stop CMD processes and ^C will not work reliably, either Sad
       Since a single cam/firm compilation takes less than 20 sec (on my Turion 1.8 GHz) can't you
       first do a test 'Compile Selected' for say your own main cam only, before going for lengthy
       multi cam/firm compile sessions ?
That's what i normally do, but sometimes i compile all sessions to check whether there are some problems, to check the compile log or to make a "All-CHDK-Package", takes ~ 15 - 30 minutes, sometimes i have to stop somewhere in the middle...  :-[

 

Related Topics


SimplePortal © 2008-2014, SimplePortal