debian crossbuild bacon

[bigbass]

Hello

special note:
this not to interfere in any way with Peter and barryk's work
I understand it is a different situation completely

but it sparked a search
I just wanted to test that idea
but using the raspberry pi3
and see what it would take to do it
if possible using a debian based solution




cross build bacon debian based option

there are a lot of confusing
ways to explain that

but for me simply it means use another compiler
and libs that are NOT part of your native toolchain
and arch to compile something.


lets say you are using a RPI3 with arm
uname -m
aarch64

there is no way you can compile a x86-64
binary because you are using arm of course!

the "normal way" would be compile on the system that has that
natively 100% is solved

but ... if you still want or have a need to build an x86-64
using a raspberry pi3

we need some more tools to do the job
and some trial and error to sort things out!

1) get the tools list
======================================
apt-cache search crossbuild-essential
=======================================

will give you a list of different compilers
I chose amd64 as my end result binary compiler


=============================================
sudo apt-get install crossbuild-essential-amd64
==============================================

I tried to find the simplest solution
NOT the official way to cross build and produce
an official debian package (maybe later if I find a reason do it with cmake)

I will use an odd folder name "Public" to the build just to
show it all in a clean place
===============================================
# manual pre step
# we get the official bacon.bac from version 4.5.0 source build
# and copy it to Public

# generate the bacon c code in the folder called build
cd Public
bacon -np -d build bacon.bac

=================================================

#now we redirect the native compier to use a new
#compiler for x86_64 remember we are on a raspberry pi3 still

cd build

#COMPILE
/usr/bin/x86_64-linux-gnu-gcc-10  -c bacon.bac.c


#BUILD  add libm.so  from the x86_64 crossbuild
/usr/bin/x86_64-linux-gnu-gcc-10 -o bacon bacon.bac.o  /usr/x86_64-linux-gnu/lib/libm.so


#STRIP
/usr/x86_64-linux-gnu/bin/strip  bacon
================================================





file bacon
bacon: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=a733a7d09bb64e2712d6e22b8cd8c8378ad75b4b, for GNU/Linux 3.2.0, stripped


this is the short result *after several failed tries
and it seems to be clean
without any compiler errors or warnings

Joe




++++++++++++++++++++++++++++++++++++++++

that was fun lets try with
crossbuild-essential-i386


file bacon
bacon: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=caeda1fdc54c35df89a71618d0921cef6ecf7d5e, for GNU/Linux 3.2.0, stripped

[Pjot]

Thanks for sorting this out Joe!

Best regards

Peter

[bigbass]

Hello Peter

Thanks

I think /hope I got it sorted correctly now with
a special cmake CROSSBUILD for bacon

I will only use one build arch for this
but making other archs is simple following this same pattern

sudo apt-get install crossbuild-essential-amd64


this is only for the raspberry pi host for x86_64 target
sourceforge.net/projects/bassix-gtk3-webkit-browser/files/CMAKE_BUILDS/CMAKE_CROSSBUILD_BACON_RPI_X86_64-4.5.0.tar.gz/download

*the reason being is cross building requires some hard coded variables
cmake is very smart and it detects your system well
for this reason we have to override the native toolkit locations
via hard coded variables for each target arch


I had about 90% of this done already with cmake builds
adding the cross build code about 10% more to get the
debian package to build too for the x86_64
and change all the needed new x86_64 toolkit code to work

P.S I hope something here could be useful in getting bacon 4.5
to work to help embedded development

Joe

same as above demo idea but skip the manual bacon -np -d build
and make part
cmake handles all that automatically now just need

the cpack is optional but builds a real debian package !



cmake .

cmake --build .

cpack













+++++++++++++++++++++++++
tech notes extra info only here
+++++++++++++++++++++++++

while it is still fresh in my memory
this is the hard coded area that needs to be changed for each new arch

UPDATED only needs arch and the package name now



snippet from CMakeLists.txt


# this CMakeLists.txt was manually generated for bacon
# by bigbass May 1 2021   updated to 4.5 Aug 26 2022 for crossbuild

#=================================
# a new variable for crossbuilds
set(CROSSBUILD_ARCH "x86_64")
#=================================


# force crossbuild
#CROSSBUILD
# which compilers to use for C and C++
set(CMAKE_SYSTEM_NAME "Linux")
set(CMAKE_SYSTEM_PROCESSOR "${CROSSBUILD_ARCH}")
set(CMAKE_C_COMPILER "${CROSSBUILD_ARCH}-linux-gnu-gcc-10")
set(CMAKE_CXX_COMPILER "${CROSSBUILD_ARCH}-linux-gnu-g++-10")
set(PKG_CONFIG_EXECUTABLE "${CROSSBUILD_ARCH}-linux-gnu-pkg-config")
set(PKGCONFIG_EXECUTABLE "${CROSSBUILD_ARCH}-linux-gnu-pkg-config")


# force crossbuild
set(CMAKE_ADDR2LINE "${CROSSBUILD_ARCH}-linux-gnu-addr2line")

# force crossbuild
set (CMAKE_AR "${CROSSBUILD_ARCH}-linux-gnu-gcc-ar")

# force crossbuild
set (CMAKE_CXX_COMPILER_AR "${CROSSBUILD_ARCH}-linux-gnu-gcc-ar")

# for the GCC compiler # force crossbuild
set (CMAKE_CXX_COMPILER_RANLIB "${CROSSBUILD_ARCH}-linux-gnu-gcc-ranlib-10")

# force crossbuild
set (CMAKE_LINKER "${CROSSBUILD_ARCH}-linux-gnu-ld")

# force crossbuild
set (CMAKE_NM "${CROSSBUILD_ARCH}-linux-gnu-gcc-nm-10")

# force crossbuild
set (CMAKE_OBJCOPY "${CROSSBUILD_ARCH}-linux-gnu-objcopy")

# force crossbuild
set (CMAKE_OBJDUMP "${CROSSBUILD_ARCH}-linux-gnu-objdump")

# force crossbuild
set (CMAKE_STRIP "${CROSSBUILD_ARCH}-linux-gnu-strip")

# force crossbuild
set (CMAKE_STRINGS "${CROSSBUILD_ARCH}-linux-gnu-strings")


# force crossbuild
# FIX needs ${CMAKE_DL_LIBS} for bacon to compile and forced crossbuild
target_link_libraries(bacon ${CMAKE_DL_LIBS}  "/usr/${CROSSBUILD_ARCH}-linux-gnu/lib/libm.so" )

# force crossbuild x86_64 hard coded package name
set(CPACK_DEBIAN_FILE_NAME "bacon_4.5.0_amd64.deb")
   





[bigbass]

one more


host raspberry pi 3 build a x86 32 bit bacon package

sudo apt-get install crossbuild-essential-i386


download the cmake build
sourceforge.net/projects/bassix-gtk3-webkit-browser/files/CMAKE_BUILDS/CMAKE_CROSSBUILD_BACON_RPI_i386-4.5.0.tar.gz/download

then just three commands


cmake .

cmake --build .

cpack


joe@raspberrypi:~/Downloads/CMAKE_CROSSBUILD_BACON_RPI_i386-4.5.0 $ file bacon
bacon: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=caeda1fdc54c35df89a71618d0921cef6ecf7d5e, for GNU/Linux 3.2.0, stripped


and builds you package
bacon_4.5.0_i386.deb

[bigbass]

Hello

what does all this mean ?

well how about we wrote something in bacon
but we want to debian package it and build it for different archs

now it gets interesting

the first will be picscale

hello vovchik you get a debian package

host rpi target !386 ( aka x86 32 bit )

sudo apt-get install crossbuild-essential-i386




sourceforge.net/projects/bassix-gtk3-webkit-browser/files/CMAKE_BUILDS/CMAKE_CROSSBUILD_PICSCALE_RPI_i386-0.1.4.tar.gz/download

then just three commands


cmake .

cmake --build .

cpack



file picscale
picscale: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, BuildID[sha1]=7da07ee7fa3c4d908ac5ac3e8b281fdf7f4bc583, for GNU/Linux 3.2.0, stripped


in the debian world now its
picscale_0.1.4_i386.deb


Joe

I numbered it that way because cmake wont take letters so "d" became a "4" abcd
the source has the long fix from Peter


moved to sourceforge easier to maintain all packages by arch

sourceforge.net/projects/bassix-gtk3-webkit-browser/files/i386-deb-packages/
sourceforge.net/projects/bassix-gtk3-webkit-browser/files/amd64-deb-packages/