On 01/28/2015 10:01 AM, Michael Schnell wrote: > On 01/27/2015 10:27 PM, Ewald wrote: >> - Without the target system, the application cannot be tested .. > This is true, only because remote debugging is not well supported.
For remote debugging a target system is needed as well? So even if remote debugging would be easy-peasy, the part you quotes still stands: no target system: no decent testing. > > In fact I sometimes to programs to be run on a headless system (e.g. a > NAS) Here you can't install Lazarus, because you don't have a GUI. [this might be an extremely silly proposition, please forgive me] Why don't you run lazarus through ssh? Or use vnc? > > You easily can install fpc and compile native, though. > > So I ended up testing the software on a PC (as far as possible without > the hardware) and finally compile it on the target system. > > I did not bother to install the cross compiler (the problem here is > not fpc itself, but the cross-libraries that are necessary link the > project for the target system). > > If I would be able to use Lazarus on the development system to > remote-debug the target system, the effort to install the complete > cross-compile infrastructure would be viable. I believe you are saying that you would like to cross-compile and debug the system remotely (which, judging from your other posts, are mostly embedded platforms?), but due to difficulties/roadblocks you are forced to compile it natively and debug it on the target system. Well, _if_ the cross-compilation works, why not just ssh in to the target system and run gdb there? Please forgive my ignorance as I do not know the exact details of your setup. -- Ewald _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
