Exactly I have 8 different targets, ALL of them are in some different stage of glibc.It's for the main reason (mucking up the host) that I avoid cross-compiles like the plague. Much easier to farm off the compilation to specific boxes.
What I do is if the target drives a UI is to build the UI on the host using GTK or FLTK, get that working exactly the way it should. Then test it on the target, if libs are installed my cmake will build it on the target. Keep in mind when you run into trouble is doing the build on your host and try to open up something like i2c-3, that is not going to work on the host so you are going to be testing on the target any ways.
Many different ways to do things, it comes down to the task at hand. Keep in mind some of the IDE's do not have remote building, only issue I run into is the doing stuff on the armhf remotely, its slow. But, I am working at a very low level and not even remotely close to being able to run on the host.I disagree. Cross-compilation seeming hard is often just a symptom of not using a proper package manager or build system.
Statistics: Posted by foxsquirrel — Mon Aug 26, 2024 1:37 am