Trouble loading contributed patches

#1

I would like to build 1.0.6
I am able to build a working latest release but then I am not able to use the contributed patches and object right?

Actually i did build 1.0.6 but no factory or contrib patches load.

I got some trouble building working version 1.0.6

I did:

git clone https://github.com/axoloti/axoloti.git axoloti/
git log
git checkout e67c36461ac1e12cab0b9c84c5034c735bf3cd

As this was the hash of the last update for 1.0.6

The the build was successful but upon loading the older firmware the board crashed and i had to put it in PFU mode to recover the firmware.
Now when i connect the board, none of the demo patches load.

I get errors like

upon connecting the board.:

java.io.FileNotFoundException: objects/synonyms.xml (No such file or directory)
java.io.FileNotFoundException: objects/transitions.xml (No such file or directory)

when trying to load a patch:

java.io.FileNotFoundException: public_key.der (No such file or directory)

export axoloti_home=/opt/axoloti

Any tips?

#2

Ok a part off the errors are gone by commenting out in > Axoloti.sh the following line:

#export axoloti_home=${axoloti_home:="$rootdir"}

Now i can load the factory patches.

But when i try to load contributed patches i get:

org.simpleframework.xml.core.AttributeException: Attribute 'appVersion' does not have a match in class axoloti.PatchGUI at line 1

So what version of Axoloti is needed to load the contributed patches and objects?

#3

~$ cat /opt/axoloti/axoloti-contrib/objects/*/*/*.axo | grep appVersion

objdefs appVersion="1.0.9"
objdefs appVersion="1.0.8"

Ah i see some need 1.0.8 and some 1.0.9

So i will revert back to 1.0.9.

#4

1.0.6 is the last 'released version'

anything after that is a 'test release', for test releases we only support the latest i.e. 1.0.9

I think next time, we will need to do this differently, Ive proposed the linux approach, which uses odd numbers as test releases and even as production releases . (I think its that way around)

e.g.
1.0.x prod
1.1.x test
1.2.x prod

this ways everyone knows 1.1 are test releases, and 1.2 production releases.

anyway, for now 1.0.9 is stable, so unless its your first encounter with Axoloti , then Id suggest 1.09

as for commenting out axoloti_home, I'm assuming you are running the shell script for some reasons, rather than using a released version? I would not change the script, but rather set axoloti_home to what you need....
but I'm not quite sure what your setup is, so cant advise on that.

#5

Hi Technobear. I amconfused by the versioning.

/opt/axoloti$ git tag
1.0
1.0.1
1.0.2
1.0.3
1.0pre17
1.0pre18

and

git tag -l "v1.0.9"
is empty

i did

git clone from https://github.com/axoloti/axoloti

and build it from there.

My axoloti patcher version shows 1.0.3-39

Am i running the latest version? or am i doing something completely wrong?

Doing checkout for 1.0.9 ...

git checkout 7357e535a4cac9d83fe16d7605d9688475ce894e
fatal: reference is not a tree: 7357e535a4cac9d83fe16d7605d9688475ce894e

I start to see ghosts :slight_smile:

I don't know but /usr/home/timbos/usr/opt a symbolic link to /opt and I modified Axoloti.sh to make it work

java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

#6

it would be 

git tag -l "1.0.9"

i.e. no v

you should be able to simply use 

git checkout 1.0.9

this will tell you its a detached head, which is fine as long as you are NOT making/contributing changes...
(as changes need to be made on a branch, currently we use master for this)

if your not seeing the tag, you need to check you have pulled the tags, this is done by default on the initial clone, but later otherwise you have to pull new ones

Ive no idea where this came from, we don't create or need this....

why are you doing anything with git here?

can you take step back, and tell me what your trying to do, and why?

Im a bit confused... /opt/axoloti is only used for the installed version, but if your are cloning the axoloti repo, then it sounds like your building axoloti, in which case this should be done in your home directory.....

Im a bit concerned, that your putting things in 'unexpected' places, which is why you are stumbling into issues....

basic process is

in your home directory,
clone axoloti
run platform_linux/build.sh
this should download all thats need, compile the firmware and then compile the java app

if you need to do just the last step, simply type

ant

(of course ideally , you could just use the pre build versions we have released on github)

#7

Thanks i will try cloning building and installing i my home dir. I moved my axoloti to opt out of good practice. Thanks for the help

#8

Sorry for being such a noob but i finally got a working build of 1.0.9 marked as version 1.0.9.g37blabla-DIRTY :slight_smile: by running:

git clone https://github.com/axoloti/axoloti.git
cd axoloti/
git checkout 1.0.9

./build.sh

cd ..
ant

git submodule update --init --recursive
git checkout

Axoloti.sh

Cheers

Tim

#9

Cool.
( the dirty indicates something has changed , but it's probably the contrib repo)

Just be slightly aware, this will operate in 'developer' mode which is slightly different from a proper release. ( mainly with how the object libraries are handled)

You can actually build a proper release with

ant -Dbuild-bundle=1

But you will need the oracle jdk to do this.