Autobuilding of trunk - page 3 - General Discussion and Assistance - CHDK Forum

Autobuilding of trunk

  • 31 Replies
  • 26095 Views
Re: Autobuilding of trunk
« Reply #20 on: 05 / November / 2011, 13:36:57 »
Advertisements
You should ask hacki about the "older version" links, I can't do anything about that.

I did - he is going to fix that when the new build completes.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: Autobuilding of trunk
« Reply #21 on: 05 / November / 2011, 17:38:58 »
Should be fixed, someone forgot that executables on linux don't end in .exe


Doh! Sorry about that :(

Phil
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: Autobuilding of trunk
« Reply #22 on: 21 / December / 2011, 01:23:15 »
In scope of finalization of flat modules project I made compile all cameras and found that following are not able to compile:

ixusW_sd430 - because require absent platform/ixusW_sd430/sub/110a/makefile.inc in $(topdir)/makefile.inc
s80 - because require absent platform/s80/sub/100g/makefile.inc in $(topdir)/makefile.inc

Is that known thing?

*

Offline whim

  • ******
  • 2046
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Autobuilding of trunk
« Reply #23 on: 21 / December / 2011, 09:08:47 »
In scope of finalization of flat modules project I made compile all cameras and found that following are not able to compile:

ixusW_sd430 - because require absent platform/ixusW_sd430/sub/110a/makefile.inc in $(topdir)/makefile.inc
s80 - because require absent platform/s80/sub/100g/makefile.inc in $(topdir)/makefile.inc

Is that known thing?

Yes, they aren't marked SKIP_AUTOBUILD for nothing ... AFAIK abandoned partial ports, kept in SVN in the hope that
people owning these cams show up and help finish them. I wouldn't worry about these cameras, they already missed out
on several major CHDK upgrades, so one more is unlikely to hurt.

Just my 2c,

wim


 

Re: Autobuilding of trunk
« Reply #24 on: 24 / February / 2012, 02:57:06 »
Seems to be the best place to ask:

What happened to http://mighty-hoernsche.de/ ?
Seems like the lase update of svn for release_1.0 was #1680 but autobuild stuck on 1659...
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

Re: Autobuilding of trunk
« Reply #25 on: 24 / February / 2012, 04:21:44 »
...and I did not find any other place to download the newest compiled versions. Please, write a short how-to, if something has changed. Thanks!
(A 410), SX 200, (SX 280), SX 700

Re: Autobuilding of trunk
« Reply #26 on: 24 / February / 2012, 05:57:57 »
Something is broken rather than changed (however this is a kind of change too) ;)
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

*

Offline reyalp

  • ******
  • 14134
Re: Autobuilding of trunk
« Reply #27 on: 24 / February / 2012, 15:46:58 »
Something is broken rather than changed (however this is a kind of change too) ;)
Do a full refresh in your browser. I see 1688 there.

The html sometimes gets cached.
Don't forget what the H stands for.

Re: Autobuilding of trunk
« Reply #28 on: 24 / February / 2012, 16:16:03 »
Oh... I feel stupid now;) mighty-hoershe was never cached this way on my browser, so I dodn't even tought about it...

Thanks!
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick

*

Offline reyalp

  • ******
  • 14134
Re: Autobuilding of trunk
« Reply #29 on: 11 / March / 2012, 19:46:40 »
Thanks to hacki, there are now two autobuilds.

Users looking for a stable version should continue to use the 1.0 release branch, found at  http://mighty-hoernsche.de

The unstable (trunk) branch is available at http://mighty-hoernsche.de/trunk/
This should be mostly functional most of the time, however users should be aware that it may occasionally be broken, and that there may be incompatible changes between builds.

The unstable branch also uses the new module system, so a complete install requires all the modules in addition to diskboot.bin and/or PS.FI*

Don't forget what the H stands for.

 

Related Topics


SimplePortal © 2008-2014, SimplePortal