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

Windows GUI for trunk building

  • 771 Replies
  • 309574 Views
*

Offline reyalp

  • ******
  • 14128
Re: Windows GUI for trunk building
« Reply #560 on: 30 / July / 2011, 16:44:58 »
Advertisements
I highly recommend that anyone doing serious work use SVN working copies, not copying whole exported trees around.

/brokenrecord ;)

As my work pattern is usually to start a port between firmware versions and not update the trunk while completing that, I have gotten used to only have a few versions around at one time and thus forgot I played with the "auto delete" that I think I originally asked you to include. 
Note that if you use svn, you can keep your working copy up to date without any worry about losing your own changes. In general, conflicts are unlikely if you aren't working on the core, and if there are conflicts, tortoise has nice tools to resolve them. This greatly reduces the chance of error when you create your patches, and ensures your work in progress stays current with the trunk.

I know this is mostly OT, but I bring it up because seems like it would be more effective to use tools that are designed to do this rather than trying to implement your own versioning system in chdkshell.
Don't forget what the H stands for.

Re: Windows GUI for trunk building
« Reply #561 on: 30 / July / 2011, 17:21:44 »
I know this is mostly OT, but I bring it up because seems like it would be more effective to use tools that are designed to do this rather than trying to implement your own versioning system in chdkshell.

I think it comes down to command line vs GUI.  And while I've been using command line tools since before Ronald Reagan came into office, its just easier to play with CHDK-Shell's GUI when jumping around between cameras and firmware versions. But that's just me.

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 14128
Re: Windows GUI for trunk building
« Reply #562 on: 30 / July / 2011, 18:25:01 »
I think it comes down to command line vs GUI.  And while I've been using command line tools since before Ronald Reagan came into office, its just easier to play with CHDK-Shell's GUI when jumping around between cameras and firmware versions. But that's just me.
To me that would be an argument for having an option to tell chdkshell "this is my working copy, let me manage what versions it contains but build here"
Don't forget what the H stands for.

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #563 on: 31 / July / 2011, 05:36:06 »
CHDK-Shell-v333 (update version)

  • changed: 'Remove old builds' code now properly keeps user selected number of
                  builds, respecting any missed downloads; also removed forced minimum
                  count (was 5, now 1)

  • added:    As extra precaution against possible loss of data there's now also
                  an option to send the removed old builds to Recycle Bin (Trashcan)
                  instead of deleting them outright (while at work, tooltip will show
                  'Recycling' and 'Deleting', respectively). Additionally, when
                  using Recycle, the "mark-for-removal" prefix ('~!~') is removed
                  to make restoring them a one step operation.
                  Thanks for the suggestions, waterwingz

  • note:      Although this should help to avoid you losing any modifications
                  you make to builds that are downloaded and unpacked by CHDK-Shell,
                  it is still highly recommended to clone the original, and make
                  your modifications in this clone (clones are never removed);
                  If you then diff this working copy with the original, you
                  should be able to create usable patches.
                  To clone a build, use the 'linked squares' icon near the 'Change'
                  button.

  • Security: Clean according to Jotti. Checksums (FileAlyzer) are:
                  CHDK-Shell-v333-sfx.exe
                  CRC-32:  04829EE9
                  MD5:      2AF83AE2731F2967F73CAF65A6A0D2B8
                  SHA1:     38C8554CF29A6D67187E0A4DB0C67B1901A1C568
                  CHDK-Shell_Updater.7z
                  CRC-32:  BB15C3F2
                  MD5:      72951C1DE55A2F80638746DDAB82851B
                  SHA1:     27714B4C3C79BF87BA84D41963B43984C71FB66C

cheers,

wim

[ Have 7z & a recent*) version ? Save bandwidth, use CHDK-Shell-updater.7z  ]

*) recent = same minor version, so currently 3.3.0 and higher
« Last Edit: 19 / August / 2011, 04:01:58 by whim »

Re: Windows GUI for trunk building
« Reply #564 on: 16 / August / 2011, 20:29:43 »
@whim - in case you miss this http://chdk.setepontos.com/index.php?topic=6747.msg71823#msg71823,  philmoz has some pretty good changes to the trunk Makefile that will possibly need a change to CHDK-Shell.

TIA

Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #565 on: 17 / August / 2011, 08:05:53 »
@waterwingz

Thanks, yes, I noticed the patch and it's consequences

wim
« Last Edit: 19 / August / 2011, 04:02:17 by whim »

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #566 on: 19 / August / 2011, 04:27:57 »
@ CHDK-Shell users

Since this morning something appears to have changed in the assembla.com SVN source pages for both CHDK and CHDK-DE: new revisions are no longer detected by CHDK-Shell, and I'll need to rewrite the HTML scraping routines. In the meantime, new revisions can be manually downloaded from this page through the "Download in other formats: zip archive" link at the bottom of the page.

wim


Re: Windows GUI for trunk building
« Reply #567 on: 19 / August / 2011, 12:57:38 »
abnormal program termination
zsh: fork failed: no such file or directory


This is unfuriating .. I am now getting that error VERY often when compiling with the Windows prebuilt environment.

In the past, the Logitech webcam driver has caused this problem !.

The only thing I have changed is to add  Borland C++ Builder to the end of the PATH environment variable.

The gcc path is after the system roots and WBEM (whatever that is).


Re: Windows GUI for trunk building
« Reply #568 on: 19 / August / 2011, 13:06:52 »
This is unfuriating .. I am now getting that error VERY often when compiling with the Windows prebuilt environment.

In the past, the Logitech webcam driver has caused this problem !.

The only thing I have changed is to add  Borland C++ Builder to the end of the PATH environment variable.

The gcc path is after the system roots and WBEM (whatever that is).

Every now and then I get the same thing - I thought it was just me.  I've assumed it is some sort of memory leak issues when I have too much stuff open ( 8G of RAM just doesn't go far these days).  The solution seems to be a reboot - simply closing and reopening CHDK-Shell doesn't seem to fix it.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Windows GUI for trunk building
« Reply #569 on: 20 / August / 2011, 04:16:08 »
@microfunguy
@waterwingz

Please note that:
Quote
abnormal program termination
zsh: fork failed: no such file or directory
indicates you're using an old version. The gcc versions I'm currently distributing with CHDK-Shell
(and separately here) do not use zsh anymore, but bash.

hth,

wim

 

Related Topics


SimplePortal © 2008-2014, SimplePortal