I don't know Lazarus, so it is probably best not to multiply my problems for the moment. I shall develop a batch script to compile everything. One way of discovering what the dependencies are!
You are not alone in that. I know many developers that prefer to do it that may.... sometimes simply for the reason that they love their programmer editor (be that VIM, Geany etc) and don't want to give that up.
fpGUI, by design, doesn't force or dictate any development tools on you. That is why everything included with fpGUI are stand-alone tools. The help viewer
DocView, the visual forms designer
UIDesigner, the image conversion tool etc.
To make compiling slightly easier from the command line, you can of course create your own build script. You could also take the idea used by the fpGUI demos and extend it to suite your needs. All fpGUI demos can be compiled from the command line via:
fpc @extrafpc.cfg <projectname>
The
extrafpc.cfg file simply contains the compiler parameters and search paths.