Why not simply select "use external editor"
QuoteWhy not simply select "use external editor"To do that you need to understand all the occult tricks the IDE does.
Like making copies of files you include in a project and all the pre-compile voodoo. It's not a case of "simply select".
Then , why not use command line compiler ; then why not use avrdude command... then remind me what is the IDE actually good for ?
Which, by the way, has some well-known and seriously screwy bugs that will result in mangling your perfectly sound sketch code into something that totally confuses the g++ compiler, and very likely you when you start trying to make sense of the resulting compiler error messages.
ARDUINO_SHELL_DIR = \Arduino\arduino-0023ARDUINO_DIR = \Arduino\arduino-0023PERL_EXE = \strawberry\perl\bin\perlTARGET = dht22_test3aARDUINO_LIBS = DHTxx2BOARD_TAG = pro5v328ARDUINO_PORT = \\.\COM14ARDUINO_MAKE = \Arduino\make\arduino-mk-0.8include $(ARDUINO_MAKE)\Arduino-W32.mk## Hopefully these will be self-explanatory but in case they're not:## ARDUINO_DIR - Where the Arduino software has been unpacked## TARGET - The basename used for the final files. Canonically# this would match the .pde file, but it's not needed# here: you could always set it to xx if you wanted!## ARDUINO_LIBS - A list of any libraries used by the sketch (we# assume these are in# $(ARDUINO_DIR)/libraries ## ARDUINO_PORT - The serial port where the Arduino can be found (only needed# when uploading## BOARD_TAG - The ard-parse-boards tag for the board e.g. uno or mega# 'make show_boards' shows a list## You might also want to specify these, but normally they'll be read from the# boards.txt file i.e. implied by BOARD_TAG## MCU,F_CPU - The target processor description
But before you dive into all that, I suggest first just trying out the "external editor" check-box option. Just to prove you really don't have to use the makefiles to use the IDE in external editor mode, you just press the build/upload button on the IDE and it does its usual build voodoo.
Yes, I looked at external editor but to do that you need to know all the tricks the IDE is doing , like moving files somewhere else before compiling.
I recently got stuffed because I referenced a file in #include and put it in the sketch directory but it was not in a "tab". This did not even flag missing (missing by the time the sketch got silently copied elsewhere) but failed because a function in the (not) included file was not defined.
That means in order to work with an external editor I need to know the ins and outs of the build voodoo.
That seems a pointless effort to me. Better spend the time setting up a Makefile so that I have a predictable , well-behaved development env.
Thanks for the posted file and the links that should save me some time.
What was the extension of the file? I've read (but haven't yet verified) that in 1.0.1, only .h and .cpp files can now be included by a #include directive from within a sketch (who knows why... the Arduino team seem hell-bent on doing all they can to subvert the expected and otherwise well-defined behaviour of the venerable C preprocessor.)
Just have to hope I can write a function prototype without my IDE nanny.