Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users - page 4 - CHDK Releases - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 3 [4] 5   Go Down

Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users

  • 41 Replies
  • 37790 Views
*

Offline Hacki

  • ****
  • 359
  • EOS 80D
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #30 on: 23 / September / 2008, 17:06:08 »
Advertisements
I'd say lets always call 'trunk' just chdk. After all, it is the version on which the most people contribute, the version most people use - special names are good for branches and forks.

About the versioning.. As we're already at 0.5, why dont pursuit a versioning method like the linux kernel guys use.. odd numbers for unstable/development releases, even numbers for stable releases.. (0.5.x for dev, 0.6.x for a stable one, 0.7.x for a dev version again..)

But honestly, i dont see the necessity for a distinction between stable & development releases.. In chdk its "either it works, or it does not". Things that doesnt work wont get commited to trunk anyway, and small things like the "sporadic raw" wont be noticed if there's only a little community of testers.

Just my 2 cents.

Regards
Logged
*

Offline fe50

  • ******
  • 3139
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #31 on: 23 / September / 2008, 18:34:34 »
Quote from: Hacki on 23 / September / 2008, 17:06:08
I'd say lets always call 'trunk' just chdk. After all, it is the version on which the most people contribute, the version most people use - special names are good for branches and forks.
ack, then we can use version numbers (Grand xxx / Allbest CHDK 50 / CHDK 0.5.x) to point to the past "versions"...
Quote
About the versioning.. As we're already at 0.5, why dont pursuit a versioning method like the linux kernel guys use.. odd numbers for unstable/development releases, even numbers for stable releases.. (0.5.x for dev, 0.6.x for a stable one, 0.7.x for a dev version again..)
But honestly, i dont see the necessity for a distinction between stable & development releases.. In chdk its "either it works, or it does not". Things that doesnt work wont get commited to trunk anyway, and small things like the "sporadic raw" wont be noticed if there's only a little community of testers.

Stable / unstable version numbers - hmm - a nice way for developers, but users often don't know the difference, furthermore we rarely have one really stable build, stable = bug free & with all the same features full functional for all cameras...

My suggestion:
* one "trunk" (the main development tree) with autobuild (=actual state)
* branches for experimenting & dangerous/unsafe features (like the current dataghost)

* a clever download page in the wikia with hierarchical links to "stable" bin packages;
  from time to time we place versions from the trunk which are looking "stable" (no or sparsely bug reports) there:
...
  -> Download: latest Autobuild (see Changelog)      (experimental)
  -> Download: CHDK build       0.5.0                (Date: xx.xx.xxxx)(stable)
  -> Download: CHDK build       0.4.0 aka "Juciphox" (Date: xx.xx.xxxx)(stable)
  -> Download: CHDK Allbest     #51 build 499        (Date: xx.xx.xxxx)(beta, with support for A380)
  -> Download: CHDK Allbest     #51                  (Date: xx.xx.xxxx)(stable)
  -> Download: CHDK Allbest     #50                  (Date: xx.xx.xxxx)(stable)
  -> Download: GrAnd's build    xxx                  (Date: xx.xx.xxxx)(stable)
...
Logged
*

Offline Hacki

  • ****
  • 359
  • EOS 80D
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #32 on: 23 / September / 2008, 18:45:07 »
Sounds good, i can host some stable releases on mighty-hoernsche.de .. maybe wrap them into a nice download page..

(And i probably should get another domain name)

Logged
*

Offline fe50

  • ******
  • 3139
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #33 on: 23 / September / 2008, 19:07:40 »
Logged
*

Offline hiker_jon

  • ****
  • 284
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #34 on: 26 / September / 2008, 21:53:40 »
Hi,

I tried downloading the sources and doing a make.  It fails for me.  (It worked on allbest 57). Maybe someone can help me figure out what is going on:

What is ../bin/caminfo.txt?

By the way there is an error in platform.inc on the A570 firmware.  The two versions are 100a and 101a (not 100e).


gmake fir
**** Build: 0.5.5
>> Entering to tools
pakwif.c -> pakwif.o
pakwif.o -> pakwif.exe
gensig.c -> gensig.o
gensig.o -> gensig.exe
-> signatures_vxworks.h
CAUTION! 'signatures_vxworks.h' is not uptated due to 'sig_ref_vxworks_1.bin` or
 'sig_ref_vxworks_2.bin` or 'sig_ref_vxworks_3.bin` is empty!
finsig.c -> finsig.o
finsig.o -> finsig.exe
<< Leaving tools
>> Entering to lib
>> Entering to lib/font
font_8x16.c -> font_8x16.o
rbf_font.c -> rbf_font.o
font_8x16.o rbf_font.o -> libfont.a
<< Leaving lib/font
>> Entering to lib/math
d2d.c -> d2d.o
wrapper.c -> wrapper.o
d2d.o wrapper.o -> libmath.a
<< Leaving lib/math
>> Entering to lib/ubasic
camera_functions.c -> camera_functions.o
tokenizer.c -> tokenizer.o
ubasic.c -> ubasic.o
camera_functions.o tokenizer.o ubasic.o -> libubasic.a
<< Leaving lib/ubasic
>> Entering to lib/lang
lang.c -> lang.o
lang.o -> liblang.a
<< Leaving lib/lang
>> Entering to lib/lua
setjmp.S -> setjmp.o
lapi.c -> lapi.o
lcode.c -> lcode.o
ldebug.c -> ldebug.o
ldo.c -> ldo.o
ldump.c -> ldump.o
lfunc.c -> lfunc.o
lgc.c -> lgc.o
llex.c -> llex.o
lmem.c -> lmem.o
lobject.c -> lobject.o
lopcodes.c -> lopcodes.o
lparser.c -> lparser.o
lstate.c -> lstate.o
lstring.c -> lstring.o
ltable.c -> ltable.o
ltm.c -> ltm.o
lundump.c -> lundump.o
lvm.c -> lvm.o
lzio.c -> lzio.o
lauxlib.c -> lauxlib.o
lbaselib.c -> lbaselib.o
ldblib.c -> ldblib.o
ltablib.c -> ltablib.o
lmathlib.c -> lmathlib.o
liolib.c -> liolib.o
loslib.c -> loslib.o
loadlib.c -> loadlib.o
linit.c -> linit.o
setjmp.o lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o lobje
ct.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o lvm.o lzio
.o lauxlib.o lbaselib.o ldblib.o ltablib.o lmathlib.o liolib.o loslib.o loadlib.
o linit.o -> liblua.a
<< Leaving lib/lua
<< Leaving lib
>> Entering to platform
>> Entering to platform/a570
>> Entering to platform/a570/sub
>> Entering to platform/a570/sub/101a
boot.c -> boot.o
stubs_min.S -> stubs_min.o
stubs_auto.S -> stubs_auto.o
-> stubs_entry.S
CAUTION! 'stubs_entry.S' is not uptated due to target firmware binary not found!

stubs_entry.S -> stubs_entry.o
lib.c -> lib.o
stubs_entry_2.S -> stubs_entry_2.o
capt_seq.c -> capt_seq.o
movie_rec.c -> movie_rec.o
mount.c -> mount.o
boot.o stubs_min.o stubs_auto.o stubs_entry.o lib.o stubs_entry_2.o capt_seq.o m
ovie_rec.o mount.o -> libplatformsub.a
<< Leaving platform/a570/sub/101a
<< Leaving platform/a570/sub
main.c -> main.o
lib.c -> lib.o
wrappers.c -> wrappers.o
kbd.c -> kbd.o
shooting.c -> shooting.o
main.o lib.o wrappers.o kbd.o shooting.o -> libplatform.a
<< Leaving platform/a570
<< Leaving platform
>> Entering to core
entry.S -> entry.o
nothumb.c -> nothumb.o
main.c -> main.o
gui_draw.c -> gui_draw.o
gui_menu.c -> gui_menu.o
gui_palette.c -> gui_palette.o
gui_mbox.c -> gui_mbox.o
gui_debug.c -> gui_debug.o
gui_fselect.c -> gui_fselect.o
gui_read.c -> gui_read.o
gui.c -> gui.o
kbd.c -> kbd.o
conf.c -> conf.o
histogram.c -> histogram.o
gui_batt.c -> gui_batt.o
gui_space.c -> gui_space.o
gui_osd.c -> gui_osd.o
script.c -> script.o
curves.c -> curves.o
raw.c -> raw.o
gui_calendar.c -> gui_calendar.o
gui_lang.c -> gui_lang.o
gui_bench.c -> gui_bench.o
gui_mpopup.c -> gui_mpopup.o
gui_grid.c -> gui_grid.o
motion_detector.c -> motion_detector.o
raw_merge.c -> raw_merge.o
luascript.c -> luascript.o
edgeoverlay.c -> edgeoverlay.o
shot_histogram.c -> shot_histogram.o
gui_reversi.c -> gui_reversi.o
gui_sokoban.c -> gui_sokoban.o
-> main.elf
   text    data     bss     dec     hex filename
 230100   13484   71280  314864   4cdf0 main.elf
zsh: permission denied: ../bin/caminfo.txt
c:\cygwin\home\jonh\gcc\bin\gmake[1]: *** [main.elf] Error 1
gmake: *** [all-recursive] Error 1

C:\cygwin\home\JonH\CHDK\trunkJP>pause
Press any key to continue . . .
Logged
*

Offline reyalp

  • ******
  • 14003
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #35 on: 26 / September / 2008, 23:35:41 »
caminfo.txt just records the memory sizes. Not sure why you would get permission denied, but you could comment out the stuff that creates it without harm.

The string "Firmware Ver GM1.00E" at (FFC08024) appears in the 100e firmware dump. The corresponding string in the other firmware dump is "Firmware Ver GM1.01A". Grand also lists it as 100e here: [DOWNLOAD LINKS] Firmware dumps available

I'd suggest that if there is a 100a, it would be yet another variant.
Logged
Don't forget what the H stands for.
*

Offline hiker_jon

  • ****
  • 284
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #36 on: 27 / September / 2008, 10:31:42 »
Hi,
I commented out the following lines in core\Makefile and it compiles now.  Thanks
Code: [Select]
# @printf " %s-%s (%s, #%s): MEMISOSIZE used: 0x%s\n" \
#   $(PLATFORM) $(PLATFORMSUB) $(PLATFORMOS) $(PLATFORMID) \
#   `tail -c16 $(topdir)size.txt | head -c6` >> $(topdir)bin/caminfo.txt
« Last Edit: 27 / September / 2008, 10:33:42 by hiker_jon »
Logged
*

Offline Cricri

  • *
  • 14
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #37 on: 01 / October / 2008, 06:20:47 »
Quote from: Hacki on 23 / September / 2008, 18:45:07
Sounds good, i can host some stable releases on mighty-hoernsche.de .. maybe wrap them into a nice download page.. (And i probably should get another domain name)

Thanks for this page by the way, I like having the option between small and complete packages :)
The domain name really doesn't matter to be honest, I believe most people wanting to check for the latest build will have bookmarked the page like I did.
Logged
*

Offline Alchemist

  • *
  • 15
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #38 on: 01 / October / 2008, 10:02:44 »
Hello all programmers,

I know myself and MANY others would still like the video added for the S5IS. Is ANYONE working on it? If I could I would, but I know nothing about programming. Hope someone can do this for all us S5 owners. Thanks.....
Logged
*

Offline chaonatic

  • *
  • 7
Re: Allbest + JuciPhoX = CHDK (the merge thread) - info for devs and users
« Reply #39 on: 18 / October / 2008, 14:43:47 »
Okay, I've asked in a thread all to itself but no one responded to it so I thought I'd plead here.  I apologize for cluttering up the dev thread but would someone *pretty, pretty please* add multipartition support for the ixus70 (please?)  I know it works because Microfunguy has it working in his ixus70 builds.  I have an 8GB card that has all but gone to waste because I can't use this wonderful firmware on it to its full potential.  If someone would be so kind as to add the code to the ixus70 build I would gladly test it for you.

Thank you very much (in advance) and sorry again to break into this thread with a request.   :)
Logged
Pages: 1 2 3 [4] 5   Go Up
« previous next »
 

Related Topics