supplierdeeply

Windows GUI for gcc toolchain

  • 37 Replies
  • 27961 Views
*

Offline msl

  • *****
  • 1224
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Windows GUI for gcc toolchain
« Reply #10 on: 01 / March / 2016, 17:51:03 »
Advertisements
update (version 0.9.276)

- Function for adding & removing of own data in the source code, e.g fi2.inc
- Upload of compiled data onto the camera via chdkptp
- More sanity checks
- Extra unzip function for source code packages, e.g. from assembla
- some small improvements

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

*

Online blackhole

  • *****
  • 518
  • A590IS 101b
    • Planetary astrophotography
Re: Windows GUI for gcc toolchain
« Reply #11 on: 02 / March / 2016, 04:24:02 »
EXPIRE_TEST option does not work properly.
Warning of an expired version is always displayed
Seems like the source code is broken.

*

Offline reyalp

  • ******
  • 10949
Re: Windows GUI for gcc toolchain
« Reply #12 on: 02 / March / 2016, 16:10:07 »
Seems like the source code is broken.
Expire test works fine for me in the latest trunk, not using the GUI. Setting it to 30 days gives "30 days left" in the splash screen.

The tool seems to output OPT_EXPIRE_TEST=1 to the localbuildconf.inc, even if the spinner is set to a different value. The value should be the number of days the build is valid for.

Maybe worth noting the tool will overwrite / delete any existing localbuildconf.inc, or making the tool warn if there is already one present.

Also, thanks msl and rudi for doing this, very nice work :)
Don't forget what the H stands for.

*

Offline msl

  • *****
  • 1224
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Windows GUI for gcc toolchain
« Reply #13 on: 02 / March / 2016, 17:34:45 »
Thanks for reporting.

The tool seems to output OPT_EXPIRE_TEST=1 to the localbuildconf.inc, even if the spinner is set to a different value.
Fixed in r277


Maybe worth noting the tool will overwrite / delete any existing localbuildconf.inc, or making the tool warn if there is already one present.
New in r278: An existing localbuildconf.inc will be saved and restored.

Download in first post of the topic.

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!


*

Offline msl

  • *****
  • 1224
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Windows GUI for gcc toolchain
« Reply #14 on: 19 / March / 2016, 08:22:18 »
Update (version 0.9.283)

- The group of localbuildconf.inc options is now divided into rubrics (maybe that helps for better understanding of the options). The layout of this group is automatically adjusted according to the number of options.

- Some small improvements

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

*

Offline msl

  • *****
  • 1224
  • A720 IS, SX220 HS 1.01a
    • CHDK inside
Re: Windows GUI for gcc toolchain
« Reply #15 on: 07 / May / 2016, 15:44:34 »
Update (version 0.9.288)

- Optimization of the rubrics
- Bugfix for processing buildconf.inc
- Generating a camera list from the platform folder when missing camera_list.csv. "Make Cam List" is not available here.
- Preliminary support for CHDK forks like SDM (needs an integration of local_buildconf.inc for optional build settings)

https://www.assembla.com/spaces/rudi_space/subversion/commits/287
https://www.assembla.com/spaces/rudi_space/subversion/commits/288

msl
German CHDK pages:  CHDK forum | CHDK inside | CHDK Twitter News by msl | Download CHDK-DE (Autobuild)
Note: SDM violates the GPL rules!

Re: Windows GUI for gcc toolchain
« Reply #16 on: 08 / May / 2016, 22:21:56 »
Finally gave this a try on a "virgin" machine - one that has never had any CHDK association.  Hit a couple of bumps that might be just me being thick.  Comments (so far) below - resolution might help the next person.

  • Downloaded the Gui.  Promptly realized I also need to download the compiler tool chain seperately.  I assume that I will also have to hunt for a capstone and chdkptp install files as well? And maybe an svn client?
  • What does "Primary" refer to?  A folder with primary.bin files?
  • What does "Open Source" try to launch?
  • It would be nice if the Windows "command box" stayed open after completion.  Right now it dies on something and I can't figure out what.

I do get an error log - I suspect that I need to set some PATH variable or something :

"C:/Users/a/Documents/Documents - Personal/CHDK/gcc493/bin/sh.exe": svnversion: command not found
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
"C:/Users/a/Documents/Documents - Personal/CHDK/gcc493/bin/sh.exe": line 2: C:/Users/a/Documents/Documents: No such file or directory
gmake[1]: *** [clean-recursive] Error 1
gmake: *** [clean-recursive] Error 1



One feature I was hoping to see is the ability to make and apply svn compatible patch files.  Not too sure I see it though?

Thanks to you and rudi for doing this!
« Last Edit: 08 / May / 2016, 22:32:46 by waterwingz »
Ported : A1200  SD940  G10  Powershot N  G16*

*

Offline rudi

  • ***
  • 123
  • A590IS_101B, SX260HS_100B
Re: Windows GUI for gcc toolchain
« Reply #17 on: 09 / May / 2016, 13:41:07 »
Hi waterwingz,

1. Downloaded the Gui.  Promptly realized I also need to download the compiler tool chain seperately.  I assume that I will also have to hunt for a capstone and chdkptp install files as well? And maybe an svn client?
For building of latest chdk, you only need GUI, compiler tool chain and of course chdk source. Capstone is only for chdk development. If you would transfer chdk after building to camera, then is chdkptp required.

2. What does "Primary" refer to?  A folder with primary.bin files?
Yes, but this path is only required for chdk development.

3. What does "Open Source" try to launch?
Opens the currently selected chdk source code folder with windows file explorer.

4. It would be nice if the Windows "command box" stayed open after completion.  Right now it dies on something and I can't figure out what.
Please use "Error Log" button or check "\bin" folder with "Open Source" button.

I do get an error log - I suspect that I need to set some PATH variable or something :
"C:/Users/a/Documents/Documents - Personal/CHDK/gcc493/bin/sh.exe": svnversion: command not found
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
"C:/Users/a/Documents/Documents - Personal/CHDK/gcc493/bin/sh.exe": line 2: C:/Users/a/Documents/Documents: No such file or directory
gmake[1]: *** [clean-recursive] Error 1
gmake: *** [clean-recursive] Error 1

An svn tool is not required for building chdk. The first message line is only a warning.
Your selected compiler (gcc493) is an arm-eabi-gcc. Your source need an arm-elf-gcc.

Notice: there are three compiler tool chains available (see first post):
  • gcc493 for arm-eabi, chdk rev. 3780 (correct "OPT_" name at 3784) or later
  • the good old gcc451 for arm-elf
  • gcc451_493 for both, requires the right setting of USE_GCC_EABI in the GUI
One feature I was hoping to see is the ability to make and apply svn compatible patch files.  Not too sure I see it though?
We use TortoiseSVN and don't plan to include a diff function.

rudi


Re: Windows GUI for gcc toolchain
« Reply #18 on: 09 / May / 2016, 14:13:54 »
Your selected compiler (gcc493) is an arm-eabi-gcc. Your source need an arm-elf-gcc.
Thanks for that.

One feature I was hoping to see is the ability to make and apply svn compatible patch files.  Not too sure I see it though?
We use TortoiseSVN and don't plan to include a diff function.
An svn tool is not required for building chdk.
I understand. I'll continue using svn on the command line on my main Linux machine.   However, for a beginner working on CHDK for the first time,  the ability to make a patch file (or apply one) at the click of a button would be pretty nice.  One less thing for them to have to learn separately.
Ported : A1200  SD940  G10  Powershot N  G16*

*

Offline dvip

  • ****
  • 451
Re: Windows GUI for gcc toolchain
« Reply #19 on: 11 / May / 2016, 14:41:58 »
First, thanks for creating CHDK-Compiler-GUI_r288. It looks good, great GUI and it loads fast.
I'm running it in Win7/64-bit but I ran into some problems.

This is what I did:

Installed in C:\chdk :
- CHDK-Compiler-GUI_r288.zip
- gcc451_ gcc451-493_ gcc493.7z
- capstone-mingw-chdk-3.0.4-patched-2016-01-11_1.zip
- Downloaded trunk-4626.zip from within CHDK-Compiler-GUI_r288

If I use GCC: gcc451 I get that a DLL is missing. See image attached.
Attached is also an image with my setup.

If I use CC:  gcc493, after clicking on "Compile", I get the following error log:

"C:/chdk/gcc451_ gcc451-493_ gcc493/gcc493/bin/sh.exe": svnversion: command not found
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
process_begin: CreateProcess(NULL, arm-elf-gcc -dumpversion, ...) failed.
"C:/chdk/gcc451_ gcc451-493_ gcc493/gcc493/bin/sh.exe": line 2: C:/chdk/gcc451_: No such file or directory
gmake[1]: *** [clean-recursive] Error 1
gmake: *** [clean-recursive] Error 1


Am I missing something?









 

Related Topics