Beta Test / Technical

[transmitterdan]

Ron,

Why do you think wx 3.1.2 is required? You ought to be able to build O or plugins with the current wx development release obtained by “sudo apt-get upgrade”.

If you want to test with wx 3.1.2 or the latest git master of wx you may have to build it from the git source.

Maybe I am not understanding your concern. I usually build both ways so I can see what problems the latest version of wx might cause. But I think O 5.0 is built against wx 3.0.x not 3.1.2.

[rgleason]

http://www.cruisersforum.com/forums/...ml#post2893624

[RonSouthworth]

Originally Posted by rgleason

http://www.cruisersforum.com/forums/...ml#post2893624

Thanks,

Just trying to figure things out. More fun with wxWidgets.

Ive only been asked to compile some plugins for mac linux so it is to cross check coding / bugs etc.

[RonSouthworth]

Originally Posted by RonSouthworth

Thanks,

Just trying to figure things out. More fun with wxWidgets.

Ive only been asked to compile some plugins for mac linux so it is to cross check coding / bugs etc.

PPA encryption is failing

[did-g]

Originally Posted by rgleason

In Appveyor.yml file under...
Then the appveyor file could be more generic, and each github user could have another file located in their top github directory that is "ignored" that they enter their encrypted public key into.

My memories are fuzzy on this one but IIRC in your user appveyor project setting environment tab you can set your own GitHub_auth_token for deploying on your github fork.

[bdbcat]

Ron...


For fun, I built wx3.1.2 on Ubuntu (gtk2) using the following config:

../configure --without-subdirs --prefix=/usr --with-libjpeg LDFLAGS=-rdynamic --enable-graphics_ctx --with-opengl --with-sdl --enable-unicode --enable-shared --disable-stc

OCPN starts and runs with this build. A couple of asserts....


Good Luck
Dave

[RickyEM]

RickyEM

[rgleason]

Originally Posted by did-g

My memories are fuzzy on this one but IIRC in your user appveyor project setting environment tab you can set your own GitHub_auth_token for deploying on your github fork.

Yes, that can be done, but I was thinking about having the appveyor file the same for the main repository and for forked repositories with other people,

so what would be ideal is the ability to put your public key in a simple file that is included in the user's repository and read by appveyor somehow when the key is needed.

I would hope that that file with the public key would not get picked up in a PR or pushed to some other repository. Don't know how this could be done.

I suppose we could just muck along as usual, but I have gotten the appveyor file so that I can push a new tag to remote and appveyor will build the artifact and then upload it to Github "Release" creating the release in the github release tab.

So the process would be to
1. Change the VERSION.cmake file Plugin_Major, Minor, Patch and Date and check the OCPN_VERSION= "ov50".
2. Then git add the changed files, commit and push that to your remote.
3. Then push a new Tag to the remote in the form "v[plugin version]-ov50"
4. Then appveyor will do all the work to make the Github "Release".

[transmitterdan]

Originally Posted by bdbcat

Ron...


For fun, I built wx3.1.2 on Ubuntu (gtk2) using the following config:

../configure --without-subdirs --prefix=/usr --with-libjpeg LDFLAGS=-rdynamic --enable-graphics_ctx --with-opengl --with-sdl --enable-unicode --enable-shared --disable-stc

OCPN starts and runs with this build. A couple of asserts....


Good Luck
Dave

Dave,

This works for Ubuntu. On RPi O crashes or more accurately locks up the session manager or the window manager. I’m looking into it.

[did-g]

Originally Posted by rgleason

Yes, that can be done, but I was thinking about having the appveyor file the same for the main repository and for forked repositories with other people,

So the process would be to
1. Change the VERSION.cmake file Plugin_Major, Minor, Patch and Date and check the OCPN_VERSION= "ov50".
2. Then git add the changed files, commit and push that to your remote.
3. Then push a new Tag to the remote in the form "v[plugin version]-ov50"
4. Then appveyor will do all the work to make the Github "Release".

Where on Github do you want to push?

1) Your fork
2) main repository


IMO 2) is a no go and 1) is currently working:
In github you create a personal access token with repo access.

you copy the token in your appveyor profile.

You can test with current WR
After pushing a tagged commit I get:

https://github.com/did-g/weather_routing_pi/releases


of course Appveyor can screw ALL your repos now, same as with secure token inside yml file though.Installer and version reported in O should use commit hash cf opencpn or it's going to be a support nightmare.

[RonSouthworth]

Originally Posted by transmitterdan

Dave,

This works for Ubuntu. On RPi O crashes or more accurately locks up the session manager or the window manager. I’m looking into it.

Thanks for the info,

I am running a development version of UBUNTU, but raspi is something im looking at for onboard use, the pi3 has some serious grunt now with my luck there is a pi 4 not too far away maybe

the repo’s can be in a state of flux at different times. Yesterday was a encryption key issue

It is handy to have the source for important libraries as sometimes updates break things, it has been pretty stable just the same.

The kernel is really fast for my really old machine which is why i use it.

/Ron

[RonSouthworth]

Originally Posted by bdbcat

Ron...


For fun, I built wx3.1.2 on Ubuntu (gtk2) using the following config:

../configure --without-subdirs --prefix=/usr --with-libjpeg LDFLAGS=-rdynamic --enable-graphics_ctx --with-opengl --with-sdl --enable-unicode --enable-shared --disable-stc

OCPN starts and runs with this build. A couple of asserts....


Good Luck
Dave

Thanks Dave,

Ive had some fun with repo’s and weirdness with the wxWidgets library source. Different file size and number of files and couldn’t get it to compile with anything close to these options i tried a lot of combinations.

So the lesson to learn is when lib weirdness happens go for checking the checksum first something Ive not seen in a long while.

I will give the config awhirl and see what happens. Noting Dans input as well

Im not building any thing for anyone with it, it is an old testing box for my purposes mostly.

Conformity of libraries for cross platform work in theory should make things more compatible not always, I know.

The config script at least is successful so that is a big improvement from the mid April hiccup

My actual personal goal is to make a test suite nothing fancy but good enough to be able to test things. 200 euro and up is a bit too big an ask, and most of the stuff it isn’t easy for the average person to use so there is a need i think....

A lot to figure out, starting with the HMI overlays first then i will code in some stuff i figured out a while ago that worked ok ( rewriting from java)

Thanks for the help as always,

/Ron

[rgleason]

This should be easy. How to start Opencpn from the Ubuntu 18.04LTS Terminal.
Opencpn looks like it installed by may not be configured for the graphics?

http://www.cruisersforum.com/forums/...ml#post2894526

[transmitterdan]

Rick,

Try this first

export DISPLAY=:0.0
openCPN

[rgleason]

Thanks TDan, did this. could not find opencpn!

rgleason@Dart:~$ find . opencpn
.
./.bash_history
./.bash_logout
./.bashrc
./.gnupg
./.gnupg/pubring.kbx
./.gnupg/trustdb.gpg
./.local
./.local/share
./.local/share/nano
./.profile
./.sudo_as_admin_successful
find: ‘opencpn’: No such file or directory
rgleason@Dart:~$