There is a default private hardware path.
I guess your helios is there.
As I said before the helios package was for Arduino 1.0. It needs
adoption. Probably not much but I can't say what you changed so I can't
comment on how expected it is that it doesn't work.
If you want I can make a helios package for you.
I would like to find out why the plugin sticked to the "old installation
path"
Jantje
Op 24/01/2016 om 0:37 schreef Wim Jongman:
I recompiled the product and then unpacked the product zip to the same location as previously with a fresh workspace.
When I added a new sketch it defaulted with my "Helios" board.txt setting that I punched in earlier. Where did it remember that?
I tried to do some Helios stuff but that did not work. Is this expected?
Then I plugged in my Uno, created a new sketch from the "Blink" example and after adding "Arduino.h" everything worked.
On Sat, Jan 23, 2016 at 9:28 PM, Wim Jongman <wim.jongman@xxxxxxxxx <mailto:wim.jongman@xxxxxxxxx>> wrote:
Sure, no problem.
On Thu, Jan 21, 2016 at 9:54 PM, Jan Baeyens <jan@xxxxxxxxxx
<mailto:jan@xxxxxxxxxx>> wrote:
yes point 5 :-)
Op 21/01/2016 om 21:27 schreef Wim Jongman:
I have been offline. Any things that require attention from me?
On Jan 21, 2016, at 15:57, Jan Baeyens <jan@xxxxxxxxxx
<mailto:jan@xxxxxxxxxx>> wrote:
A small update on the progress
1) Get Teensy to work nicely
Done (Add [teensyduino]/hardware/teensy to private paths
It works but the platform.txt needs to be modded. Paul
will (if test turn out ok in teensyduino) change this in
teensyduino 1.2.8 (no idea when that will be released)
2) fix for 325
Done. I think this is a cool feature.
I want to add a turn on/off functionality in case things
go wrong (default on)
3) board name- port-baut rate in project explorer (like
the version control tools do but I don't find how :-( )
Done but I skipped the baud rate for a cool reason
4) complete #349
Done.
I want to add a turn on/off functionality in case things
go wrong (default on)
5) fix for 347
Done
But I would like input from wim on "why is the plugin is
still using the old location".
Can you debug
it.baeyens.arduino.common.getInstallationPath() on your
system? Please...
I think this may be related to the things in 7
6) documentation (all your items)
Still open
7) testing
Kind of like started as we are now on the nightly.
2 people (both linux) reported problems which look like
failing dowload
https://github.com/jantje/arduino-eclipse-plugin/issues/353
https://github.com/jantje/arduino-eclipse-plugin/issues/354
Seems like there is some issue left there.
I also would like to fix 311 (normal build does not
generate .ino.cpp)
This because default now a build is started and that one
fails if you have a ino project which is any project
stated from a sample.
Best regards
Jantje
Op 16/01/2016 om 20:10 schreef Jan Baeyens:
Good to see there is a +1 for merging.
Following things I would like "done" before releasing
1) Get Teensy to work nicely
2) fix for 325
3) board name- port-baut rate in project explorer (like
the version control tools do but I don't find how :-( )
4) complete #349
5) fix for 347
6) documentation (all your items)
7) testing
of which 1 is something I'd like for merging but I fear
that won't work out fully.
I have made a wiki page on the release process :-)
https://github.com/jantje/arduino-eclipse-plugin/wiki/The-release-process
more below
Op 16-1-2016 om 19:03 schreef Wim Jongman:
+1 for merging. When do you want to release and what isI'm well endowed in ccm with several tools (f.i.
still pending for this release?
Since you can now see the beauty of branches, how about
using git flow. I am happy to give anyone a short
demonstration and some general background on git's
internal structure (as far as i know it ;).
clearcase clearquest, rtc) but I seem to have a problem
with git terminology. So yes a demonstration would be great.
What are the things that still need to be done?
### Documentation.
* New and Noteworthy for this release
* How does the workflow change for someone that
currently has a Arduino IDE installed?
* 3.0.0 FAQ
* Website changes?
### Fixes
* The long path problem
* Keeping hold of the installation path
* Moving the install_path application parameter to a
java property?
I'm not sure what you mean with
* Keeping hold of the installation path
* Moving the install_path application parameter to a
java property?
On Fri, Jan 15, 2016 at 11:54 PM, Jan Baeyens
<jan@xxxxxxxxxx <mailto:jan@xxxxxxxxxx>> wrote:
I'm not sure what you guys think about it but I
feel it is about time to push branch "big change"
to the "master" branch.
I think we increased the user experience and the
version is stable enough to make it the nightly.
I propose to make a branch 2.4 -just before pushing
big change to master- just for sakes of history.
Best regards
Jantje
<a
href="https://www.freelists.org/list/eclipse-arduino-dev>eclipse-arduino-dev@xxxxxxxxxxxxx
<mailto:eclipse-arduino-dev@xxxxxxxxxxxxx></a>
