CHDK Forum
CHDK Development => General Discussion and Assistance => Topic started by: msl on 13 / February / 2016, 10:10:08
-
The CHDK-Shell is a little bit obsolete. Newer chdk developments are not usable with the CHDK-Shell. That was a reason to create a new simple GUI for compiler tasks.
The main features are:
- Download and unpack the most recent source code revision (trunk & release)
- Path settings for GCC, Capstone, Source Code, Primary Root
- Camera selection for the compiler
- Creation of a local camera list for batch compiling
- Setting and writing localbuildconf.inc based on buildconf.inc from the recent source code
- CMD window with GCC support
- Error detection for compiler run
- Sanity checks for compiler and source code
- Insert & remove of own data in source code
- Upload CHDK files to the cameras
Download GUI (https://forum.chdk-treff.de/download/file.php?id=2853) Version 0.9.323 (recent Version)
Tested for Windows 7, 8, 8.1 & 10, 32 or 64 bit. Windows XP is not recommended, but works mostly. Copy the exe file in a folder of your choice. Blanks and special characters should not be used in the path (also for path settings in the GUI). The GUI uses the Windows standard zip function for unpacking the source code. This is very slow. Alternatively you can use 7zip. Copy the 7za.exe (http://7-zip.org/a/7za920.zip) in the GUI folder.
Also the standard gcc toolchain 4.5.1 for the CHDK shell is a little bit obsolete. The new finsig thumb2 tool works not correctly with old toolchain. (Fixed in r4539.) rudi has made a new toolchain based on gcc 4.9.3. This works properly.
Download gcc compiler Version 4.9.3 (https://chdkde.app.box.com/s/kj6qz4rbio/file/413803707369)
alternative compiler package with 4.5.1, 4.5.1-4.9.3, 4.9.3 (https://chdkde.box.com/s/nt29wodvkkd2zfpxwdrsae4d08jwxhpr)
alternative compiler package from Whim with gcc451_493_host481 (https://chdkde.box.com/s/qx1qzt61kwbohnaz747zzr6fiohwe2lg)
More Toolchains from Whim (https://chdkde.box.com/s/4c8kqofdf3s477jr9hk353sbzmwu4yf5) => https://chdk.setepontos.com/index.php?topic=12752.msg145097#msg145097
Sorry, all shared Box.net links are broken.
gcc931 working toolchain (http://downloads.chdk-treff.de/tools/gcc931_host920.7z)
Capstone tools => https://chdk.setepontos.com/index.php?topic=12752.msg140405#msg140405
Description:
All buttons and checkboxes have a short description as a tooltip.
Set the path for the compiler, is stored in the ini file. It is checked whether the compiler is valid.
Set the path for the Capstone tools, is stored in the ini file. It is checked whether Capstone is valid.
Set the path for an alternative dir with the firmware dumps, is stored in the ini file. It is checked whether dumps are valid.
Set the path for the CHDK source code, is stored in the ini file. It is checked whether the source code is valid.
Download the most recent source code as a zip file. You can choose trunk or release version. After download the file is unpacked in the folder 'trunk' or 'release' as a subfolder.
You can choose a zip file with the CHDK source code, e.g. from assembla, and a destination. After that the zip file will be unpacked in the destination.
Opens the CHDK source code folder in windows explorer. See also 'Source'.
Opens a new window with a list of the available cameras for the recent CHDK source code you have chosen. Make your selection of cameras. The selected cameras are saved in a local list (local_camera_list.csv). With the Button 'Compile List' you can compile all cameras from this list.
Function for uploading of the CHDK files onto the camera. At the first use the path to chdkptp must be set. If chdkptp.exe is available, you can choose a zip file. After a security question the file will be unzipped. As next starts the upload of the unzipped files to the camera.
- User Source, Insert User Source, Remove User Source.
Adds the subfolder 'user source' in the program dir. In this folder you can place additional files, e.g. fi2.inc. Use the same folder structure as in the CHDK source code. These additional files can be inserted into the recent CHDK source code or again removed.
Set the checkboxes for your private compile options. Some checkboxes are activated only when the conditions are met. These options are checked: FI2, GEN_STUBS, GEN_SIGS, USE_GCC_EABI, CAPSTONE_TOOLS, PRIMARY_ROOT
Compiles the chosen camera/firmware depending on checkboxes 'full' and 'clean'. If errors are present, the error log can be read. Use the Botton 'Error Log'.
Compiles all cameras listed in camera_list.csv depending on checkboxes 'full' and 'clean'.
Compiles all cameras listed in local_camera_list.csv depending on checkboxes 'full' and 'clean'. See also 'Make Cam List'.
Opens a cmd window with the GCC environment in the source code path.[/list]
GUI source code (https://www.assembla.com/spaces/rudi_space/subversion/source/HEAD/CHDK_Compiler_GUI/trunk)
Thanks:
rudi for his help. Whim for the great program CHDK Shell: http://chdk.wikia.com/wiki/CHDK-Shell reyalp for capstone tools: https://chdk.setepontos.com/index.php?topic=12714.msg126204#msg126204 reyalp for the wonderful chdkptp: http://chdk.wikia.com/wiki/PTP_Extension#chdkptp
msl
-
The CHDK-Shell is a little bit obsolete. Newer chdk developments are not usable with the CHDK-Shell. That was reason to create a new simple GUI for compiler tasks.
Works great, thanks for your hard work guys! ;)
-
Nice, thanks rudi :D
The new finsig thumb2 tool works not correctly with old toolchain.
What's the problem? I think I tried this when I first checked it in, but I usually use msys for the host compiler so I might have broken it since.
If using capstone, it is very important to use the patched version, like http://chdk.setepontos.com/index.php?topic=12714.msg126351#msg126351. (http://chdk.setepontos.com/index.php?topic=12714.msg126351#msg126351.) You could include this with the tool packages if you want.
Also note the thumb2 tools assume capstone 3.0.4 (+patch above), not the "next" branch in the capstone github. The "next" branch is incompatible in some ways (different include paths, some instruction IDs changed)
-
What's the problem? I think I tried this when I first checked it in, but I usually use msys for the host compiler so I might have broken it since
There was one problem in finsig_thumb2.c: typedef struct sig_rule_s {
...
} sig_rule_t;The host compiler from the toolchain 4.5.1 could not interpret this. It was time for a new host compiler. Now is all fine.
All other things are ok. We can build the stubs_entry.S for the SX280 without any problems.
msl
-
Good work!
I think this topic should be pinned (aka sticky).
-
How does downloading source code work? I just get *Not connected to the Internet* when I try it. Do I need to be logged in somewhere?
-
A password is not needed. The program checks your Windows internet connectivity via the file connect.dll (this file is a component of windows). When the connect.dll says 'no internet', you get this message.
Which Windows version is on your machine?
msl
-
I have Windows XP SP3
-
Using Windows XP is not the best idea. ;) This was also the problem. The connectivity check works only for Vista or higher.
I have added an exception for XP. Try the updated version.
msl
-
Updated version works nicely. Thank you
-
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
-
EXPIRE_TEST option does not work properly.
Warning of an expired version is always displayed
Seems like the source code is broken.
-
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 :)
-
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
-
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
-
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
-
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!
-
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 (https://chdk.setepontos.com/index.php?topic=12752.0)):- 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
-
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.
-
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?
-
Ok, for me the problem occurs when using gcc451_ gcc451-493_ gcc493.7z. Using gcc493-host481.7z works fine. 8)
-
A couple of obvious little things for the benefit of the next person :
1) When you install the compiler, you need to update your computer PATH environment variable.
Instructions here : Compiling_CHDK_under_Windows : The_environment (http://chdk.wikia.com/wiki/Compiling CHDK under Windows#The_environment/)
2) If you don't have an SVN client installed, you will get this error message several times during the build process :
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2Fvv3dXwp.png&hash=d0241dd7495a9c71334ae49ed8a34f07)
You can safely ignore it. Or download and install Tortoise SVN to make it go away.
-
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 (https://chdk.setepontos.com/index.php?topic=12752.0)):- 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
How do we know if source requires EABI tool chain ?
What are consequences of not setting option USE_GCC_EABI correctly ?
How do we install and use Capstone ?
Thanks.
-
How do we know if source requires EABI tool chain ?
What are consequences of not setting option USE_GCC_EABI correctly ?
How do we install and use Capstone ?
EABI is necessary when GCC 4.8 or higher is used. For the compiling of a DIGIC 6 camera is necessarily GCC 4.8 or higher required. See also https://chdk.setepontos.com/index.php?topic=12115.msg118870#msg118870
Capstone is the new signature finder tool (thx reyalp), needed for DIGIC6 development. All you need is the Capstone library and settings buildconf.inc/local_buildconf.inc (The GUI makes this for you). Read more about Capstone in this post: https://chdk.setepontos.com/index.php?topic=12714.msg126204#msg126204
msl
-
Thanks for the info & links.
-
Only some suggestions for the next new Windows GUI for gcc toolchain (edited: CHDK-Shell GUI was whim's program) update:
- Remember the camera list if the user switches trunk.
- Have an option (a check box) to build the full version or the small version when clicking on "Compile List". It may save some time when generating zips.
- Keep or "remember" the main window's position/size when you exit the program (no that important but good to have).
Where is the source code for the new CHDK-Shell GUI? It looks like AutoIt script.
Again, great job!
-
Only some suggestions for the next new CHDK-Shell GUI update:
FWIW .. CHDK-Shell is a program written by whim. An different program than what is described in this forum thread.
-
>FWIW .. CHDK-Shell is a program written by whim.
>An different program than what is described in this forum thread.
OK, is it called: Windows GUI for gcc toolchain?
-
OK, is it called: Windows GUI for gcc toolchain?
I don't know what the authors rudi (https://chdk.setepontos.com/index.php?action=profile;u=11052)/msl (https://chdk.setepontos.com/index.php?action=profile;u=687) want to call it. But CHDK Shell (http://chdk.wikia.com/wiki/CHDK-Shell) is a different program entirely.
-
- Remember the camera list if the user switches trunk.
You can copy the user list in another source code. We want to keep the code as simple as possible. Remember the list needs a checkup in the next source code. Are all cameras available?.
- Have an option (a check box) to build the full version or the small version when clicking on "Compile List". It may save some time when generating zips.
This is available - option 'full'. Please note the tool tips of the GUI elements.
- Keep or "remember" the main window's position/size when you exit the program (no that important but good to have).
Agreed.
Where is the source code for the new CHDK-Shell GUI? It looks like AutoIt script.
Have you read the first post? ;) => https://www.assembla.com/spaces/rudi_space/subversion/source/HEAD/CHDK_Compiler_GUI/trunk
By the way, the CHDK shell has over 10k lines of code, because whim has fulfilled every wish. That was great. But which also has the disadvantage that updates are no longer possible. The goal of this GUI is, to keep the code as simple as possible.
Another thing. The new default forum theme is a disaster - sorry. E.g. formatting with the list tag is so not more really readable.
msl
-
Another thing. The new default forum theme is a disaster - sorry. E.g. formatting with the list tag is so not more really readable.
I keep forgetting that there is a new theme. I setup my profile to revert to the old one.
-
I keep forgetting that there is a new theme. I setup my profile to revert to the old one.
I'm too. But not everywhere I have an automatic login. I need a simple theme which is readable on PCs and mobile devices without of any facebook or other social media listings on the start site. Tapatalk is not an option for me. I hate such data collector. But that's another discussion.
Sorry for the offtopic.
msl
-
@msl,
>You can copy the user list in another source code...
Thanks for the tip.
>Are all cameras available?
Yes, as far as I know.
>This is available - option 'full'. Please note the tool tips of the
>GUI elements.
I did try that, but still get the both the full zip and the small zip. When clicking on "Compile List" and "Full" is checked.
I just want the full zip to be created. Don't need the small one.
Good to have this if it saves time, but no big deal if it keeps the program simple.
>The goal of this GUI is, to keep the code as simple as possible.
Good point.
Thanks again!
-
I did try that, but still get the both the full zip and the small zip.
Ok, now I understand the problem. That's more a thing of the makefile procedure in the CHDK source code. Also the different naming of the zip files is not quite ok.
msl
-
I keep forgetting that there is a new theme. I setup my profile to revert to the old one.
I'm too. But not everywhere I have an automatic login. I need a simple theme which is readable on PCs and mobile devices without of any facebook or other social media listings on the start site. Tapatalk is not an option for me. I hate such data collector. But that's another discussion.Sorry for the offtopic.msl
Hi,
The site has been like this for years now, I guess. The visible change of the facebook page timeline is more visual/feature than anything - the "like box" was already there, so was the code. The is no change in any of the information that was available before, the recent topics remain at the center column. Also, on the website's main page, on the top right of the central content columns you can find two tiny "-" buttons: these hide each of the sidebars.
As for mobile, the mobile theme apparently was good enough for light browsing.
That said, if you have suggestions/critique, please create a topic on the Forum Related issues board, I won't get notifications from this thread.
Cheers!
-
msl,
I'm so thankful that you kept this project going for all these years. I was able to use it to compile some improvements that I needed to write a CHDK script to photograph the recent total solar eclipse with the EOS-M3 attached to a telescope. I couldn't have done it without you (or without reyalp, ant, and all the others who contributed to the CHDK project)!
I did notice that after succesfully compiling, I always get this error:
/usr/bin/sh: svnversion: command not found
It's not a big deal, but if you know how to correct the problem easily, please let me know.
=====
Here's the solar eclipse time lapse that you helped make possible:
-
A very nice video.
I think the error is a gcc toolchain issue. You can try to copy the svn*.exe files from a tortoise svn installation to the bin dir of the gcc toolchain.
Unfortunately I cannot reproduce this problem (Win10, installed tortoise svn, gcc 4.9.3 - see the first post, recent chdk source code).
msl
-
OK, thanks for checking on it. I don't have tortoise svn installed, so that's probably it. It's not really a problem other than the error message.
-
The CHDK Shell is outdated and will not work anymore.
Try this: https://chdk.setepontos.com/index.php?topic=12752.0 or http://forum.chdk-treff.de/viewtopic.php?f=7&t=3512
Thanks for your help. Unfortunately, in the first post no pictures of the settings can be seen anymore.
I have everything installed so far. I get same error on WIN7 when compiling:
/usr/bin/sh: svnversion: command not found
But my PRIMARY.BIN is empty…
I don't have tortoise svn installed, so that's probably it.
I also not.
-
The error is unimportant for the compiling. It is more a problem with the correct version of the svn.exe and the versioning.
Have you checked the bin folder for the compiled CHDK version in the source code directory (...\trunk-5216\bin)?
A empty PRIMARY.BIN is ok. The empty file is created during compilation.
The capstone folder is only optional for developers.
You can activate the following options in the GUI:
DE_VERSION -> usefull for german language as default language
FORCE_LUA_CALL_NATIVE -> default active
msl
-
Have you checked die bin folder for the compiled CHDK version in the source code directory (...\trunk-5216\bin)?
I've overlooked ;) Thanks again...
My first CHDK build :)
**** Firmware creation completed successfully
\-> CHDK_DE-m3-101a-1.5.0-5216.zip
The capstone folder is only optional for developers.
I want to be prepared for the M100 port ;)
-
I made a build of capstone 4.0.1 which is compatible with the windows toolchain. Available from https://app.box.com/s/qqooc6yuofo8c9rnwafnxiu0stism7ij
md5sum
11d1ccf1cb2b8375433f1d2911402818 capstone-mingw32-chdk-4.0.1.zip
Unlike 3.x, no source patch is required, but the builds provided on the capstone download pages are not easily usable with the GUI and windows toolchain.
This package was built by starting a command prompt from the GUI, running bash in the command prompt, and then running
MAKE_JOBS=1 CAPSTONE_ARCHS="arm" CAPSTONE_STATIC="yes" ./make.sh
PREFIX=/d/devel/capstone-mingw32-chdk-4.0.1 CAPSTONE_ARCHS="arm" make install
where /d/devel... is the directory that will be used to make the zip. The contents of include/capstone were then moved into the include directory, to match the structure expected by the GUI.
The MAKE_JOBS=1 setting appears to be required for the build to work in mingw shells.
Anyone using the capstone tools in development should update to 4.0.1. I plan to remove capstone 3.x support soon.
-
Thanks for making the new capstone build for the GCC GUI.
Can you check your download link. My browser says it is a wrong address, mayby a c/p error.
msl
-
Thanks for making the new capstone build for the GCC GUI.
Can you check your download link. My browser says it is a wrong address, mayby a c/p error.
It works for me https://app.box.com/s/qqooc6yuofo8c9rnwafnxiu0stism7ij
Tested in an incognito window to be sure it wasn't a login issue.
There is a somewhat confusing message: "We're sorry, this file type is not currently supported" but that only means there is no preview, you can still click the download button.
-
Ok, thanks for testing. It was my mistake. My "pi hole" ad blocker has blocked box.com. Is it all fine.
msl
-
Hi @msl (and other GCC GUI users)
I prepared an alternative compiler suite gcc451_493 for use with the GUI,
with the following changes/additions:
* use GCC 4.8.1 as host compiler
* added Tortoise SVN utilities (win32) , no more error popups.
* added reyalp's latest capstone build
Unfortunately, I don't have any cloud space or server, so it will be here:
https://www.sendspace.com/file/pbf4ok (~ 40 MB)
(will be auto deleted in 30 days, around May 15)
stay safe,
wim
-
Hi Whim,
nice to see you again. :)
Thanks for your work. I have made a cloud backup: https://chdkde.box.com/s/qx1qzt61kwbohnaz747zzr6fiohwe2lg
msl
-
I made a build of capstone 4.0.1 which is compatible with the windows toolchain. Available from https://app.box.com/s/qqooc6yuofo8c9rnwafnxiu0stism7ij
md5sum 11d1ccf1cb2b8375433f1d2911402818 capstone-mingw32-chdk-4.0.1.zipUnlike 3.x, no source patch is required, but the builds provided on the capstone download pages are not easily usable with the GUI and windows toolchain.
This package was built by starting a command prompt from the GUI, running bash in the command prompt, and then running
MAKE_JOBS=1 CAPSTONE_ARCHS="arm" CAPSTONE_STATIC="yes" ./make.sh
PREFIX=/d/devel/capstone-mingw32-chdk-4.0.1 CAPSTONE_ARCHS="arm" make installwhere /d/devel... is the directory that will be used to make the zip. The contents of include/capstone were then moved into the include directory, to match the structure expected by the GUI.
The MAKE_JOBS=1 setting appears to be required for the build to work in mingw shells.
Anyone using the capstone tools in development should update to 4.0.1. I plan to remove capstone 3.x support soon.
Hi @msl (and other GCC GUI users)
I prepared an alternative compiler suite gcc451_493 for use with the GUI,
with the following changes/additions:
* use GCC 4.8.1 as host compiler
* added Tortoise SVN utilities (win32) , no more error popups.
* added reyalp's latest capstone build
Unfortunately, I don't have any cloud space or server, so it will be here:
https://www.sendspace.com/file/pbf4ok (~ 40 MB) (will be auto deleted in 30 days, around May 15)
stay safe,
wim
thx @reyalp & @whim
Additional backup: I've added those two archives to the "Development" section of the CHDK (https://drive.google.com/folderview?id=0B08pqRtyrObjTy11Y003Sk1lYTQ#list) repository.
-
@msl
Hi,
Some suggestions for CHDK Compiler GUI:
- fix missing logging for 'compile list' & 'compile all'
- auto-add svn revision to buildconf.inc
- (commented) changes are in 'BatchCompile' and 'CheckSourceCodeDir'
- bumped program code to 0.9.289
enjoy,
wim
attached: full source + changes, 7-zipped
edit 6-5-2020: removed attachment
-
@whim
A little late. ;)
Thanks for your work. I have provide your version as the recent version. The release number comes from the assembla commit number.
Stay healthy.
msl
-
Anyone tried to get colorized console output with gcc 4.9.3 using option "fdiagnostics-color" on Windows?
-
@msl
Thanks, I'm working on some more modifications. When done I'll PM you, that way you & rudi can check them without any 'release pressure'.
keep up the good work,
whim
@Ant
Tried, but so far without success ...
-
@msl
@fe50
To all (windows)home-compiling CHDKers
Hi,
Discovered while revisiting arm developer (https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads)
there's a new version of arm-none-eabi-GCC, i.e. 10.2.1
It is named "Version 10-2020-q4-major (released Dec 11, 2020)",
indicating it should be more stable than the previous release
which was marked "preview".
So, I got to work and cut & pasted together a new windows toolchain,
using the latest mingw32 host compiler, mingw32-gcc v.9.2.0
Tested working OK with Windows GUI in a "Compile All" and
tested resulting binaries on 3 of my cams.
Dowload here on sendspace gcc1021_host920.7z (https://www.sendspace.com/file/prrhoj) (link valid up to ~ March 8 )
(download button worked for me even with javascript blocked (noscript)
but the site said I had to enable it :D )
If wanted I could upload others, just let me know:
[edit] more uploaded toolchains
gcc1021_host481.7z (https://www.sendspace.com/file/idelps), gcc931_host920.7z (https://www.sendspace.com/file/m2vqd6), gcc831_host920.7z (https://www.sendspace.com/file/9hh1qe) (links valid up to ~ March 8 )
All toolchains are 70-80 Mb in (compressed to ~10%) size
have fun,
wim
-
To all (windows)home-compiling CHDKers
GCC 10 from my previous post (gcc1021_host920.7z) is not functioning
as it should for vxworks cameras, checked on Digic 2 (a630) and
Digic 3 (ixus70_sd1000).
It compiles fine, but the resulting binaries do not run at all.
(no LED activity at all, camera seems DEAD !)
GCC 9 (gcc931_host920.7z) DOES produce working binaries.
For verification I also tested binaries compiled on my linux box
(Manjaro 20.2.1 with arm-none-eabi-gcc v10.2): dryos cams run fine,
while vxworks cams are playing dead, just like on Windows ...
So, if your 'compile program' includes VxWorks cams, please avoid GCC 10.x
Not all Digic 3 cams are VxWorks - Digic 3/DryOS works (checked on A495)
sorry about that,
wim
PS Older GCC 10.1.1 does not work either.
Edit 24-03-2021: Problem was resolved in trunk revision 5796- thanks to @philmoz and @reyalp :)
-
The link to download the GUI in the first post no longer works.
It looks like we don't have alternate download locations.
-
The link to download the GUI in the first post no longer works.
https://forum.chdk-treff.de/download_dev.php :)
-
The link to download the GUI in the first post no longer works.
https://forum.chdk-treff.de/download_dev.php :)
I don't see a link for GUI there, only compilers. :(
-
The link to download the GUI in the first post no longer works.
https://forum.chdk-treff.de/download_dev.php :)
I don't see a link for GUI there, only compilers. :(
... CHDK-Compiler-GUI_r323.zip is appended @ ::)
https://forum.chdk-treff.de/viewtopic.php?f=7&t=3512&p=31563&hilit=compiler#p30971
-
Thanks!