Topic: Debugging in a folder other than where a project is built
I just downloaded and installed SF today and found it very easy to set up, build and run my main research code by moving the executable into the "working directory" where all the data files are kept. The source code is kept in a different directory as well. I do it this way because I often work with several compilers at the same time and there is a project directory for each compiler, some of which have IDEs like SF. They all reference a single, separate source code directory. It's helpful to compile new or revised code with several compilers because they all seem to flag issues that a different compiler doesn't consider troublesome. The executables built with different compilers are distinguished with appropriate add-ons to the name, and I can quickly compare results from the different builds in the working directory.
This approach works well until I wish to use the debugger. It appears that in order to use SF's debugger I would need to create the SF project in the directory where I ultimately want to run the program, so the build and module directories would need to be there too, plus the makefile and project file. Is there an alternative that would allow me to keep development in one directory and use the debugger with the executable running in a different directory?