Glade 3.20.will not work with LinuxCNC , please follow this for 3.8.6

I am working with Jessie and glade 3.8.5 build from sources with 64 bit and all is working fine.

So IMHO it is related to your distro.

Norbert

newbynobi wrote: I am working with Jessie and glade 3.8.5 build from sources with 64 bit and all is working fine.

So IMHO it is related to your distro.

Norbert

Well I tried 4.9.4 which is stated to be "tested" same issues.

I would much prefer to use Mint over Debian so I'm not chasing drivers all the time. Especially touchscreens.
what kernel are you running?
uname -r

EDIT: That is right why I also really hate Debian. uname, ifconfig etc... commands don't exist.... UGGH

As there seem to be some problems on installing glade 3.8.6 on Mint 64 bit, I tried and had success. So here is a little HowTO, based on a installed:

to get your kernel version, open a terminal and type:

Check if there is a glade version installed from the package manager, if so, you need to uninstall that release!
You may use synaptic for that purpose.
If you do not know how to do that, do not go on with this How To, as you will not be able to finish this with success!

Make sure you have all the latest updates installed. open a terminal and enter :
(just leave the terminal window opened, as you will need that one very often)
First we need to install some dependencies, just enter in the terminal:
get the source of glade 3.8.6 (Do not use any newer glade release, as they so not support gtk2 any more!)
in the terminal enter: now install it by typing:
to test the glade install, enter in the terminal:
Try to add a main window and in that window any widget you like,
if it does work, then go on

Till now we do not have any hal widgets, so we need to install linuxcnc!
So now fetch the source of LinuxCNC:

in the terminal enter:
as dpkg-checkbuilds needs assess to the source packages and as default the corresponding repositories are not enabled,
open synaptic from main menu, goto settings, packages and enable source code, check the corresponding box
close it and change to the terminal, enter
you should get:
go on in the terminal
should give something like:
so install that dependencies (check what dependencies your system really does need)

Check again, if all dependencies are satisfied:
in the terminal enter:
should give no output!

as in my case ./configure gave some errors of additional missing packages,
I needed to do:

now in the terminal enter:
gave me some warnings, but no error
go on in the same terminal:
if that is also OK, we need to copy the hal widget glade catalog to the correct place.
backup the originals first
in the terminal enter:
now copy/add the missing files to that dir with the following terminal commands Now test in the terminal you did the command
. ./scripts/rip-environment, just enter
Voila!
You should have a working glade_3.8.6

I would appreciate, if someone could add this tutorial to the official documentation or at least to the glade section.

Regards Norbert

Thanks Norbert will try it.

You do have the order of things differently. And did not try 3.8.5

BUT please test this. Issue was not widgets. It was this.
Open glade-3
Add a main window
Add an About window (or any other window I tried)
Instant crash

Yours doesn't?

Hallo,

I tested as rip environment with GladeVCP widgets, and also with normal glade without the hal stuff.
In both cases I do not have any crash. I can also open i.e. gmoccapy.glade and add stuff.

As said, I am using 3.8.5 and haven't tried jet 3.8.6

Norbert

newbynobi wrote: Hallo,

I tested as rip environment with GladeVCP widgets, and also with normal glade without the hal stuff.
In both cases I do not have any crash. I can also open i.e. gmoccapy.glade and add stuff
Norbert

Please pardon my continued questions... Just trying to fully understand. To me a RIP is meant more to test something rather then install it. Is there a reason you are doing rip with the HAL and regular without? Or just stating what you tried?

I use RIP for everything. If I'm compiling from source, there is no need to create a deb to install it when it might change next week.

rodw wrote: I use RIP for everything. If I'm compiling from source, there is no need to create a deb to install it when it might change next week.

So when you guys say RIP... You are simply saying installation without using a DEB? Acronyms... So many Acronyms

RIP means Run In Place

Basically it means run LinuxCNC without installing it in the normal locations
but rather running it from where ever it was built

This has the advantage the you can easily run multiple versions of LinuxCNC on the same host
and test versions without disturbing a working system.

The minor disadvantage of RIP installs is that you must run the RIP script that sets up the paths
and environment variables before launching LinuxCNC. I'm pretty sure the GUI launcher does this
however

Hallo subawarm,

i do it with a rip installed LinuxCNC, because on this machine I have not installed a realtime kernel. I am not sure, but starting glade-3 without doing the rip-environment step, IMHO will not allow to load the hal widgets. That's the only reason I do it this way. My machine is running with Jessie and realtime kernel and on that machine I have it is working in both ways, but I compiled on that machine LinuxCNC with relatime Preempt kernel.

Norbert