Running IDE Action item vs shelling out to command like compiler with switches?

I apologize that I am still in the learning phase with FB. But in looking at the action list, these "IDE wizards" seem to duplicate the project options screens of the IDE you are working with. So I can check all the boxes and save an action that builds the project with the correct option like whether debug is on or not, symbols included, etc. All of these options are things that each compiler lets you specify if you know what they all are. So it seems that you could either use the Action for each compiler and set it up that way, or just shell out with an action that runs any EXE program and run the compiler with all of the switches that you need.

I'm not clear as to the benefit of using the visual wizards. Can anyone shed light as to why I might want one way or the other? My current batch file method just calls the exe that runs the compiler and sends it a bunch of switches. I noticed with our Delphi XE compiler, that when I do a build based on my settings, the list of options could almost not be generated by a human it is so long.

The whole point of FinalBuilder, and the UI for the actions is that you don’t need to know what all the command line options are. The delphi action makes a reasonable attempt to provide a similar UI for the compiler options to delphi (well up to D7 at least), and it’s spits out the command line options for you. Whilst you might be familiar with the command line compiler, most developers are not, especially the newer developers. FinalBuilder makes it much easier to modify the build without spending a bunch of time finding the help topics for each command line option. It reduces the “bus factor” by not requiring specialized knowledge in order to manage the build process.