Hopefully it will give some hints as to the calls used to extract the (.hex) filename and the device name, the documentation for the compiler output is something I have not seen listed and it took me some time to figure them out. If you are using another programmer the portion of the line which invokes the programmer and sets the parameters for the programmer would need changing. I'm using the NSDSP programmer (nsprog.exe). hex file name to program the target device. Hopefully this will prevent those preferences from being lost.īeing spurred on by another thread, I've managed to create a "command line" that calls the GCB compiler directly, and invoking the programmer with the correct. Worse still, my preferences are often overwritten when updating, something that makes me reluctant to upgrade. It also means that where an error is found during compilation the G+STools window stays open which means it has to be closed to return control to the Geany window, and a re-compilation can't take place until this window has been closed. This has the downside of not showing the full compilation information in Geany once the compilation has completed. I've previously used the GCB "tools" for compiling my programs. I have a preference for using Geany as my GCB IDE rather than SynWrite.
0 Comments
Leave a Reply. |