Unfortunately, according to our internal tests, it simply doesn't work acceptably enough without the latest components. I am doing my hardest to erradicate as many operational problems as possible ready to coincide a release with the next OS4 update.
I guess that's one of the problems with improving the OS to do what you need :)
I've just re-installed my OS4 after a HD crash ... :( ... And installed CodeBENCH to continue development on AmiDARK Engine ;) That's why I was thinking about the 0.9 upgrade you mentionned in a post on these forums :p
I'll wait (im)patiently for these upgrades :p
Regards, Fred
All we have to decide is what to do with the time that is given to us.
Unfortunately, according to our internal tests, it simply doesn't work acceptably enough without the latest components. I am doing my hardest to erradicate as many operational problems as possible ready to coincide a release with the next OS4 update.
I guess this comment from Rigo still aplies as OS4.1.1 hasn't been released yet.
I hear that you are working on a GUI for the GNU debugger ? Is this a part of CODEBench or is it a stand alone application? Anyways, I have suggested a bounty for a GUI on AmigaBounty, as this is one of the things, I wouls REALLY like to have!
(Of course, the current version of the debugger is completely unusable as it is, so maybe this has to be fixed first...)
IIRC correctly there was already some work done (and screenshot shown) by an IBrowse dev be it Stefan or Robert so it can be done (and it's the way it is done in the (powerfull) graphical debugger 'ddd' under Linux). Do you know what happened to this initiative ?
GDB *is* powerfull we only need a reliable one which does not crash the system once and then while attaching to a process or while loading (or trying to) symbols of some system librairies. Then we will need a frontend for it.
Yes, I know of that program, but Stephan apprently made changes to the machine interface of gdb in order to get his GUI to work properly. It was very much a WIP, it was based on MUI and I had some problems with it.
gdb is just an archaic donkey which is bloated with loads of crap not applicable to the ELF format.
Rigo : gdb could be useful, we've used it this week-end at the Alchimie show (found my bug with a human debugger ... thank you for your suggestion Fab
Several people here were using CodeBench and we talked about it. We would like to have the new version now ... unfortunately it is not available. We are impatient to use it, CodeBench has a very high potential.
As I said earlier, it relies on changes to the BOOPSI gadgets that will only be available in 4.1 update 1, so a release before then would be pointless. Unfortunately, this also means that V0.9 will only run under 4.1.1, but as it will be a free download, there should be no problem.
Thanks for your continued support, and we hope to have a release ready to coincide with the OS update.
Thanks for your reply. We know that we have to wait for the next update coming with the OS one. I just want to remind you that CodeBench is appreciated and we are impatient to use the next version :)
Rigo : Just a wish that I would like in CodeBench : compilation profiles.
For example, I want to use GCC for the OS4 version of a project and vbcc for the 68k version of this project. A profile would contain the compiler name, the linker name, their options, etc. It would also help to declare a profile without debug and another one with debug.
We could have several profiles and a current one, with the possibility to switch.
Yes, in the same project. It is just an idea but you're right, it is possible to have this kind of behaviour with 2 projects even if I think it would be less efficient.
Prepare to receive other other suggestions when I will use it more deeply