Qt on OSX cross compiler for PI

[DavidHux]

Thank-you for the info.
Since I do not run Linux on a PC i thought my best chance would be to use the following script:

http://visualgdb.com/tutorials/raspberry/qt/embedded/

linked to by the QT Raspberry Pi Beginners Guide (and I therefore thought would have some hope of working)

All went well (at least no failures) until I got to the step:

7.0 Launch the msys shell from the MinGW toolchain by running <sysgcc>\MinGW32\msys\1.0\msys.bat:

This failed - with an sh.exe stopped working - no windows help provided - but last message in terminal window was`:

204 [main] sh5876 sync-with`-child: *** child state waiting for longjmp
sh: fork: Resource temporarily unavailable

and the us.stackdump ended with (probably corrupt stack)

a google on msys indicates a lot of problems (is this a W10 problem?)

Help!!

[SGaist]

Hi and welcome to devnet,

Are you trying from OS X or from Windows ? In either case, I'd recommend the use of e.g. VirtualBox and make a virtual machine with Linux on it (e.g. Kubuntu). That will make the cross-compiling way easier.

[DavidHux]

Yes I am working on Windows 10 - I would prefer not to add yet another system (real or Virtual)!

I tried looking for msys on Windows 10 - but no success so far!

Thank-you for the thought - as a real last resort!

David

[DavidHux]

@SGaist
Thank-you for the advice on =reflection:

I have installed Ubuntu 14.04 LTS (in Parallels).
I installed the QtCreator package which came with it.
I can ssh to my raspberry.

But when I tried to set up QtCreator to cross compile (Tools/Options/Devices) it failed to test connect to my Pi - never had this problem before in previous attempts to set up a cross compiler e.g on OSX and Windows! )

OK - so I removed it and went to the Wiki 'Install QTCreator on Ubuntu' - I now find that Ubuntu will not execute .run files, again a google search reveals a large number of 'do this or that' none of which work (for me)!

I feel I am running out of options!

David H

[SGaist]

Might be a silly question but: can you ssh from OS X or from Ubuntu ?

[DavidHux]

@SGaist

Yes I can ssh from Ubuntu to Pi (and from OSX and from Windows)

David

[SGaist]

What error are you getting from Qt Creator when connecting to your Pi ?

[DavidHux]

@SGaist

I do apologise, I should have included this before - I get

Setting up QtCreator to cross compile (Tools/Options/Devices) it failed to test connect to my Pi

SSH connection failure: SSH Protocol error: Server and client capabilities don't match. Client list was: aes128-cbc,3des-cbc.
Server list was aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com.

Device test failed.

Thank-you for your interest

David H

[SGaist]

What Linux flavor are you running on the Pi ?

[DavidHux]

@SGaist
I am running Jessie on the pi

[SGaist]

Ok, sounds right, what about Qt Creator ? Which version is it ?

[DavidHux]

I am just rebuilding the Linux system, I will let you the exact details when that has finished - it was the QtCreator which comes with the Ubuntu 14.04 package library!

David

[DavidHux]

@SGaist

The Qtcreator is:

Version 3.0.1 - based on Qt5.2.1(GCC 4.8.2, 64bit) Apr 9 2014 at 09:1259

[SGaist]

Might be a bit old, I'd try with 3.5.1 before anything else.

[DavidHux]

@SGaist

Hmmmm.

I am running UBUNTU 14.04LTS in Parallels on a Mac-mini

The Mac Mini CPU is an Intel Core 5 (which I would assume is an i386 and not an AMD)

The files installed for qtcreator as listed in packages.ubuntu.com are for an AMD64 machine (/usr/lib/x86_64_linux_gnu/...).

Also the ubuntu list shows that Qtcreator after 3.0.1 are under development.

This does not look right!

In any case I have just seen (doc.qt.io) that Qt 5.0 no longer includes a Windows Platform, and suggests that I should wait for Wayland

I think all this means that I should go elsewhere, so thank-you for you time and interest, it is much appreciated.

David

[jsulm]

Core i5 is for sure x86_64 and it can execute i386 binaries as well.
Because x86_64 was invented by AMD and later implemented by Intel as well it is often called AMD x86_64.