This pr is possible way to proper upstream binary release.
It is capable to create jar, which contains several crosscompiled .so files (aarch64, ppc64le and x86_64).
The first two commits "Reformated pom.xml to acomodate profile indentation" and "Separated native and java profiles in pom.xml" can go in, they can do no harm, and are necessary to fix https://github.com/chflood/jigawatts/issues/25
The last - the crosscompilation itself -commit is buggy as it is - See commented out "-static" from gcc call, so it obviously fail to run later. I had failed to crosscompile and even compile agaisnt criulib staticaally. @chflood does it evenhave sense? Is it possible in current criu setup? is it possibl eat all?
This pr is possible way to proper upstream binary release. It is capable to create jar, which contains several crosscompiled .so files (aarch64, ppc64le and x86_64).
Originally I first wanted to implement https://github.com/chflood/jigawatts/issues/25 But I found that current autotools is unable of proper cross-compilation and to fix it overcommed my autotools expertise (https://github.com/chflood/jigawatts/issues/26) and @gnu-andrew will need to help.
The first two commits "Reformated pom.xml to acomodate profile indentation" and "Separated native and java profiles in pom.xml" can go in, they can do no harm, and are necessary to fix https://github.com/chflood/jigawatts/issues/25
The last - the crosscompilation itself -commit is buggy as it is - See commented out "-static" from gcc call, so it obviously fail to run later. I had failed to crosscompile and even compile agaisnt criulib staticaally. @chflood does it evenhave sense? Is it possible in current criu setup? is it possibl eat all?