Cross compiling WxWidget application for Debian64 and Debian

[VdBergh.Paul]

I'm building a WxWidget application targetting both Debian 64-bits and Debian armhf (Raspberry). I'm using eclipse as IDE running in a Debian 9.4 Virtualbox. The VB Host is Windows10.

The eclipse workspace is organized as tree projects :

• - one project set up for Debian 64-bits architecture
  - one project set up for Debian armhf architecture (using multiarch)
  - one project with common source files.

In both the 64-bits as the armhf projects, the source code is linked in from the common project.

I installed WxWidgets for 64-bits with the following command:

Code: Select all

sudo apt install libwxgtk3.0-dev

Now, the 64-bits project compiles without errors and the executable works fine under Debian64.

Next, I like to cross-compile for armhf, so

Code: Select all

sudo apt install libwxgtk3.0-dev:armhf

Now, the armhf project compiles without errors and the executable works fine on the Raspberry Pi.
However, the compilation of the 64-bit project is broken...

Apparently, the platform specific setting for WxWidgets are defined/declared in a file called

Code: Select all

    setup.h

this file is located at

Code: Select all

    /usr/lib/PLATFORM/wx/include/gtk2-unicode-3.0/wx/

where PLATFORM is either

Code: Select all

 x86_64-linux-gnu

for Debian64 or

Code: Select all

arm-linux-gnueabihf

for Debian armhf.

My observation is that installing one version of the development package installs the correct setup.h, but also removes the other...
So, how do I setup WxWidgets for multi-arch compilation for both platforms?

Thanks in advance,

Paul

[stevepusser]

If I understand you correctly, you want to have both versions of the -dev package installed at the same time. That's not possible, as you have found out. The normal procedure is just to install the version for your target arch before the compilation, which will remove the other version. It seems to be working for you already, so I really can't see what the problem is, especially when the changeover can be scripted.

If you set up chroots with QEMU for the different architectures, it's supposed to be possible to build in those, too. At least looking at some docs for sbuild...