You are viewing a static version of the site. Enable JavaScript to benefit from the
full functionality of this site and enable such things as forum posting.
Big updates
matt:
You may have noticed that I have been overhauling my packages recently. I have just pulled in the entirety of my testing repository into the live repository, so expect things to break. Please tell me the moment you see any problems.
Systems affected:
ESP32
ESP8266
Arduino AVR
Arduino megaAVR (new).
You may have to install some new packages that an update won't install, such as python
and esp-elf2bin
.
ullix:
Some strangeness in update:
Using Ubuntu I have recently updated uecide when it became available through the ubuntu repositories. New version was 0.11.5 (at least so it said). I have never manually updated!
Today I see a new uecide update available in the repositories. But look what it says in the synaptics updater (see picture): The installed version, which claims to be 0.11.5 is listed as 0.11.4 (and the new one as 0.11.7).
Did you forget to set some variables? Is the new one supposed to be *.7?
matt:
Odd. I never use synaptic so I don't know what it's like, but everywhere I see 0.11.7 (in the internal "About" page, on the splash screen, and in apt-cache show
:
$ apt-cache show uecide
Package: uecide
Status: install ok installed
Priority: extra
Section: embedded
Installed-Size: 38478
Maintainer: Matt Jenkins <matt@majenko.co.uk>
Architecture: all
Version: 0.11.7
Depends: default-jdk
Description: Universal Embedded Computing IDE
One IDE to rule them all, one IDE to find them.
One IDE to bring them all, and in the darkness bind them.
Description-md5: 10620b629184b679f0e62b2bc134b49b
Homepage: http://uecide.org
ullix:
but this defect is not about future *.7, but about current *.4 or *.5, whatever it really was.
Synaptics shows what apt shows; it uses apt. So, my apt shows:
$ apt-cache show uecide
Package: uecide
Version: 0.11.7
Architecture: all
Maintainer: Matt Jenkins <matt@majenko.co.uk >
Installed-Size: 38478
Depends: default-jdk
Homepage: http://uecide.org
Priority: extra
Section: embedded
Filename: pool/main/u/uecide/uecide_0.11.7_all.deb
Size: 32963780
SHA256: d980d9915fee22cf3d153b40fa7ff2fc76ef704bc944507df355808286c81bcf
SHA1: 5c74d5b64202ead605c1c2c2973e6ed1a79498d2
MD5sum: 2ecdfcaeacb4fb77e871c6efc055133c
Description: Universal Embedded Computing IDE
One IDE to rule them all, one IDE to find them.
One IDE to bring them all, and in the darkness bind them.
Description-md5: 10620b629184b679f0e62b2bc134b49b
Package: uecide
Status: install ok installed
Priority: extra
Section: embedded
Installed-Size: 31512
Maintainer: Matt Jenkins <matt@majenko.co.uk >
Architecture: all
Version: 0.11.4
Depends: default-jdk
Description: Universal Embedded Computing IDE
One IDE to rule them all, one IDE to find them.
One IDE to bring them all, and in the darkness bind them.
Description-md5: 10620b629184b679f0e62b2bc134b49b
Homepage: http://uecide.org
It also is showing the installed one as *.4, while the - one and only - installed one claims to be 0.11.5:
$ /usr/bin/uecide --version
UECIDE Version: 0.11.5
P.S. how can one post code-like text on your forum and keep it in proper format?
matt:
Place code between three back-ticks or indent it 4 spaces (Standard Markdown syntax - there's a link just below the comment box...)
The version numbers are all taken from a common file, though conceivably there could possibly be a disjoint between the portions of a script. It depends exactly when I update that file I guess. Anyway, there's next to no differences between versions .4 and .5 anyway - and even less between .5 and .7 (you notice there's no .6 - I did get confused with my counting, the lockdown is getting to me I think...)
What UECIDE reports is direct from the file that the packaging scripts use to set the version, so whatever UECIDE says is correct.
ullix:
Problems: need an urgent fix now!!!
Updated uecide to 0.11.7 and the upgraded all packages via P-manager. Restarted. Tried to compile a script, which did compile right before all updating with this result:
• Linking sketch...
‣ Generating bin file...
Unable to start process
Cannot run program "ERR" (in directory "/home/ullix/Code/uecide/am_0.4_04-23a/build"): error=2, Datei oder Verzeichnis nicht gefunden
‣ Generating parts file...
Unable to start process
Cannot run program "ERR" (in directory "/home/ullix/Code/uecide/am_0.4_04-23a/build"): error=2, Datei oder Verzeichnis nicht gefunden
Compiling finished.
Memory usage
• Program size: 0 bytes
• Memory size: 0 bytes
• Compilation took 22,588 seconds.
Uploading firmware...
Unable to start process
Cannot run program "ERR" (in directory "/home/ullix/Code/uecide/am_0.4_04-23a/build"): error=2, Datei oder Verzeichnis nicht gefunden
Looks like it is missing file "ERR" and such a file or similar is not present in build!
By the way, compilation usually took 7 ... 8 sec for this script, not 22 as now?
At least uecide/apt/synaptics agree on this being version 0.11.7. However, you seem to have introduced another version quirk in the changelog:
Changelog
**0.11.7**
Bundled up-to-date base packages
Fixed missing tool vc. Prevent prototypes being added for non-ino files
Release **0.11.5**
Merge branch 'master' of github.com:UECIDE/UECIDE
Add escapes for quotes in windows command execution
Get dnsjava from Maven
New version of Launch4j
matt:
Ignore messages about versions in the changelog. That's an artefact of how the packaging works. The release message often appears in the next version if I don't do a commit of the updated version file before doing a release. It's meaningless.
I am assuming you are on esp32 or esp8266? You have to (as I have mentioned in multiple posts) manually install the python
tool. And maybe the esp-elf2bin
package too.
This is all because the esp cores, in their wisdom, suddenly decided to switch to pure python (eaugh!) for loads of their build process, whereas before they either bundled pre-processed files or used C programs compiled. That meant that I had to come up with a way of shoehorning Python in to Windows machines, which meant a tool package. For all other operating systems the tool just points to the system installed python, but there isn't one in Windows of course. And a quirk of UECIDE means that an upgrade of a package doesn't install any new dependencies (a problem I am working on at the moment for version 1.0.0), so you have to manually install them.
ullix:
I am using only the ESP32.
What name does the python tool have, and where do I find it? Where do I find theesp-elf2bin package?
matt:
It's called python
and you find it in the plugin manager. Simplest is to just type python
in the search box.
Or from the command line you can run uecide --install=python
And the same for esp-elf2bin (which I think may only be for esp8266 anyway).
ullix:
Oh, that python! Installed, and it works again. The esp-elf2bin is not installed (and obviously not needed for my ESP32). Thanks.