Compiling with different databases

[sbjqad]

We have a requirement to compile different parts of our code with different databases. Our code is devided in modules, and at compile time we generate a datebase for that module. Every module needs to have the same database name because at runtime they all connect to the same database. We can't generate one database to compile all modules because then we get ambiguity errors from the compiler. It would be good if we could have multiple "buildPath" entries in the json config file, each with their own database and build output folder. As a quick solution a call to a procedure before and after the compile procedure in thread.p could help too. That way we can connect to the correct database at compile time. I also tried compiling parts of the code separately and then include it in the propath at runtime. Unfortunately then the code is not is sync with the .r file and the debugger shows the wrong line. I tried to solve this with generating debug-list files. When I do that it shows the dbg file in the debugger and it shows the correct line numbers, but it does not see that dbg file as a source file and then I can't add breakpoints etc...

[gquerret]

More or less duplicate of #316, I will answer there.