From schroot to croos compile

XolYnrac

Hello everyone.
In our project we were using schroot to build our project.

The OS installed in the schroot is an old version of Debian and 32bits that is the same as the production environment. Additionally, it has all the library packages necessary for building.

We have also built some mkspecs that are used in the build process and which invoke external tools such as xsdcxx.

The compilation can be done by entering the schroot or by invoking the necessary commands inside the schroot from the host through a wrapper, but in both cases, the compilation is actually done inside the schroot.

All is working fine, we even have another schroot with a more modern Debian for a target with modern specifications (like arch = amd64).

Now we have the need to use code analysis tools such as Parasoft or SonarQube Scanner, but they do not work if the compilation is done in the schroot.

Searching the net I have seen that cross compile would solve the problem. That is why I turn to you hoping for guidance on where to start

Thank you very much

Pd:

We are using qmake

Targets are:

debian 8 with 32bits intel and qt4.8
debian9 with 64bits intel and qt5.10
rapsbian with armv8 qt5.10

SGaist

Hi and welcome to devnet,

Can you explain the issues you get with these tools ?

XolYnrac

@SGaist
build-wrapper-linux-x86-64 tool of Sonarqube report in the build-wrapper-dump.json:

{
"version":"6.41",
"captures":[
{
}]}

SGaist

@XolYnrac for all three targets ?

XolYnrac

@SGaist
the first two yes, the last dont was tested

SGaist

Can you explain how you are using it in your workflow ?

XolYnrac

@SGaist

the comand line is

xolynrac@developer:/mycodedir/build-wrapper-linux-x86-64 --out-dir outputdir make debug

where make is executed( through a wrapper) into a schroot that have /mycodedir mounted en the same path.

I have tried build-wrapper-linux-x86-64 compiling a local small code and that works fine, the file build-wrapper-dump.json (resulting file of build-wrapper-linux-x86-64) contain captures.

That is the reason that I need to pass to crooscompile.

I apreciate your guiadance

SGaist

@XolYnrac wait... that is a static code analysis tool. Why do you want to run it when compiling for different architectures ?

That said, don't they provide a 32bit wrapper as well ?