Windows GUI for trunk building [currently v. 3.42]

[whim]

@madman

Check your directory structure below 'trunk1632latest' against another revision that does work.

@waterwingz

Thanks for filling in - only have access to an Ubuntu machine ATM

wim

[madman]

Hmm, am I missing something?
Had working trunk/trunk1631, then checked out latest trunk into that folder.
In result Shell gives an error.

[whim]

Hmm, am I missing something?
Had working trunk/trunk1631, then checked out latest trunk into that folder.
In result Shell gives an error.

Hi,

I think I now understand your problem - maybe you want to import a revision that no longer is the latest ?
I would do this as follows:

1) goto the SVN "Browse source' page for trunk: https://trac.assembla.com/chdk/browser/trunk

2) Near the top right of the page, find the input box marked "View revision"

3) Type revision number followed by Enter

4) Scroll down to bottom of page, at the center you'll find "Download in other formats: Zip Archive"

5) After downloading find the zip - it will probably be called "trunk-r1632.zip"

6) Rename it to "trunk1632.zip" and copy or move it to {CHDK-Shell install directory}/archives

7) In CHDK-Shell, click "Unzip archive .." and select  "trunk1632.zip"

Hope that helps,

wim

PS Adding an easier method to import 'back issues" is on my list - for the moment, however, I have other fish to fry:
No access to a functioning Windows computer, and stuck in mountain snow (60 cm and still snowing)

[madman]

Will try to clarify using a question

What I need to do in order to have latest SVN trunk working with Shell?
IMPORTANT: tortoiseSVN is used  to get and update latest trunk.

[msl]

What I need to do in order to have latest SVN trunk working with Shell?

Install the shell incl. GCC into a folder of your choice. Start the shell. The program does all settings for you. With an internet connection you get the latest trunk revision. Close the shell.

Go into the trunk folder and create a new folder, e.g. trunk_work. With tortoise you can now checkout in this folder a copy of the recent trunk revision. Use this address for checkout: http://subversion.assembla.com/svn/chdk/trunk/

Start the shell, click the button 'change' & select your created folder.

msl

[madman]

That's exactly same I was doing before.
Tried again.
Same result -> error.

[waterwingz]

That's exactly same I was doing before.
Tried again. Same result -> error.

As whim is essentially offline for a while,  did you try looking at the referenced line number from the error message to see what its choking on ?

[madman]

Checked both v3.40 and v3.42.
Error refers to different lines (different code) in those versions, while same code exists in both.
I suspect that reported line number may not be correct for compiled AutoIt script.

The error is located under

Code: [Select]

Func Sanity_Check()and looks to be related to GCC compiler version checks.

[whim]

Checked both v3.40 and v3.42.
Error refers to different lines (different code) in those versions, while same code exists in both.
I suspect that reported line number may not be correct for compiled AutoIt script.

The error is located under

Code: [Select]

Func Sanity_Check()and looks to be related to GCC compiler version checks.

Doesn't work that way, unfortunately ...  during 'compilation' compiler directives, empty lines & line continuations are removed;
you would need to compensate for that. Would be fairly easy to check if I had access to the intermediate files generated during compilation, but that is not the case ATM, sorry.

[Edit: Another approach would be to run the program interpreted, which will only work if you have AutoIt (3.3.6.1 or newer)
and the full SciTE (aka SciTE4AutoIt3) installed:
- Copy the source code to where the executable is, and open it in the editor (SciTE)
- Press F5 to run it, and do whatever you need to do to provoke the error
- The error should now be reported in SciTE's lower pane, with a meaningfull line number ]

However, if you can upload an archive with your 'trunk1632latest' I'll have a look at what might be upsetting CHDK-Shell,
since (based on waterwingz' and msl's feedback) I don't think the program is at fault.

@waterwingz

Wouldn't say 'offline', but rather 'offwindows'

cheers,

wim