Closed GoogleCodeExporter closed 9 years ago
Maybe, it would help, after starting the ide, to delete all directories made by
arduino oldern than 1 week, 1 day or something like that.
Original comment by Wilfried...@googlemail.com
on 5 Oct 2012 at 11:50
This seems to be new behavior in 1.0.1; 1.0 deleted the temp directory. In
fact, 1.0 deletes the build directory even if it was specified in the
preferences file (build.path=/tmp/applet) 1.0.1 no longer deletes that,
either...
Original comment by wes...@gmail.com
on 5 Oct 2012 at 2:27
I notice this on my install also. Arduino 1.0.2 on Windows 7.
Each time the Arduino environment is run I get a build*.tmp, console*.tmp and
untitled*.tmp folder created. When I compile my Camera Axe project the build
folder has 1.16MB of data files. My temp folder over time gets littered with
garbage left behind by the Arduino environment.
The Arduino environment should delete ALL temp files it creates upon exit.
temp means "temporary". not permanent.
If there is something you want to keep around, then have an options setting to
save those debug "log/status" files in a specified directory. Also weather or
not those file(s) should be kept.
Original comment by norman...@gmail.com
on 29 Nov 2012 at 2:32
This issue still exists in Arduino 1.0.3 on Windows 7.
build*.tmp, console*.tmp and untitled*.tmp folders created in the TEMP folder
for the account. * is some random 19 digit decimal number.
When I open Arduino and do nothing but close immediately the build*.tmp folder
is deleted on Arduino exit. The others remain.
If I open a sketch of mine and do a verify and then exit. The build*.tmp folder
stays behind with all the compiled files.
untitled*.tmp has a folder inside it named with the default new sketch name
Arduino creates as default on open. e.g. sketch_dec19a
console*.tmp has two files. stderr and stdout.
After a few weeks of playing with Arduino I had about 50 sets of each temp
folder littering my system TEMP folder. Arduino should clean up after itself.
Original comment by norman...@gmail.com
on 19 Dec 2012 at 7:10
This is due to the optimization as detailed in
http://code.google.com/p/arduino/issues/detail?id=638.
Prior the IDE's "pseudo MAKE" did a clean build on every COMPILE and destructs
the temp files, as to start over. Which actually on slower systems or with
extensive Anti-Virus was noticeable. Paul's patch appears to have been
incorporated at 1.0.x. Which does not delete the temp files. And uses there
persistence to perform a build more like a refresh, rather than a clean build,
much faster. Hence the files need to stay around between builds. in the
preference turn on the verbose output for compilation and you see just the
difference.
However, it no longer deletes any of the temp files. At least for windows.
Hence they build up. And I like to compile little changes, a lot.
It sure would be nice if the arduino.exe deleted is temp that it created, when
it got the close signal.
Original comment by mpfl...@gmail.com
on 23 Dec 2012 at 5:26
I don't know if is similar problem with Linux. I don't use it much, doubt it. I
suspect that such temp files are placed in volatile /tmp drive space, not
surviving power cycles.
Original comment by mpfl...@gmail.com
on 23 Dec 2012 at 5:33
any changes for this item?
Original comment by Wilfried...@googlemail.com
on 5 Sep 2013 at 8:27
It would be good if this temp location was configurable. Also would be good if
the random-named-folder could be avoided, changing it to always use the same
predictably- and sensibly-named folder. That way you'd only ever have a single
set of files, and accessing them from other programs would be much easier.
Original comment by yer...@gmail.com
on 1 May 2014 at 12:03
https://github.com/arduino/Arduino/issues/1061#issuecomment-105535131
Original comment by federico...@gmail.com
on 26 May 2015 at 2:03
Original comment by federico...@gmail.com
on 26 May 2015 at 3:27
Original issue reported on code.google.com by
Wilfried...@googlemail.com
on 5 Oct 2012 at 11:48