Evaulation questions

guest · Post by **guest** » Fri Jan 27, 2006 1:56 am

I currently use either Mingw Developer Studio or Code::Blocks (C/C++), neither of which is acceptable because both are buggy. I like this approach but I don't see how to compile an entire project and if/or you keep up with the changes for a recompile. Also, I'm having a problem figuring out how to configure for GDB. I'm running on Windows, by the way. I'd pay money for a decent IDE but I'm not willing to pay for Borland, etc.. Some tutorials on this sort of thing would be very useful, for instance, using Zeus with GCC/GDB on Windows. Or even some default settings you could load. Anyway, any help would be appreciated. In the meantime I'll keep searching. Thanks!

Post by **jussij** » Fri Jan 27, 2006 3:18 am

I like this approach but I don't see how to compile an entire project
and if/or you keep up with the changes for a recompile.

The Zeus design assumes you already have some sort of working build process. For example your build process could be as simple as a batch file or as complicate as a set of make files or maybe even some other third party build tool.

Provided you currently have a way to build your project from the command line, you easily incorporate this build process into Zeus using the Workspace Options menu and entering the build command line into the Make Command Line entry field of the Project panel.

The build process can the be run from within Zeus using the Workspace, Make menu with the resulting output being captured to the Zeus project window.

Note that there are in fact three build command line options, Make, Rebuild and Clean and these correspond to the Workspace menus of the same name. The project settings are also divided into Release and Debug configurations (ie see top left corner drop down found in the Workspace Options dialog) and you can set the currently active configuration using the Workspace, Select Active Poject menu. So all in all there are six build command lines available for use

Also note that the Workspace Options menu contains a Compiler panel and this can be used to define the command line required to compile and individual file. So the project panel defines how to build all the files in the project, but the compiler panel defines how to compile just one file.

There is also a Compiler command line option found in the Options, Document Type menu and this is here specifically to allow a file to be compiled without having to first define a Project/Workspace.

For example when any file is compiled, Zeus first check to see if the file is part of the currently active Project/Workspace. If so it uses the compiler command line options found in the workspace. If the file is not part of the project workspace, the compiler options found in the Document Type will be used to compile the file.

For more details on how this all works refer to these links:

Also, I'm having a problem figuring out how to configure for GDB.

There is the zDebugger\xdbGcc.html file found in the Zeus install directory that shows how to use the GDB debugger from within Zeus.

The debugger support in Zeus is quite and old feature and definitely needs some re-work

But based on the limited feedback I have had regarding this feature (compared to other Zeus features), I am not sure if this is a widely feature

Feel free to comment on what could be better with the current debugger support. All user suggestion make their way to the Zeus todo list and in most cases they eventually make their way into the editor.

Cheers Jussi

guest · Post by **guest** » Fri Jan 27, 2006 3:50 am

Thanks! No, I need a project development/debugging system. I suppose I'm going to have to suck it up and pay big bucks but keep up the work. Don't let the free software junkies overtake you or we're ruined. I'm just now realizing that. We're settling for mediocre when we were used to diamonds. Software socialism!