Missed a -o in there, but hopefully you get the point ;) On Thu, Jun 29, 2017 at 10:36 AM, William Hermans <[email protected]> wrote:
> > On Thu, Jun 29, 2017 at 10:12 AM, mzimmers <[email protected]> wrote: > >> Hey, William...thanks for the pointers. I actually do already have >> cross-development working (for user space programs). I'm using Qt Creator, >> and a Linaro toolchain and sysroot. I built Qt for the armhf in order to >> get the right qmake.conf file, and I can cross-debug using gdbserver on the >> BBB. So, I've got that going already. >> >> But, as you're aware, cross building for kernel stuff is more involved, >> and I'm inclined to agree with you that I'm making this a bigger deal than >> it is. I'm prepared to move on, though I'd really like to know why this >> example program isn't working. But, as I mentioned, this isn't a BBB >> problem, so I'm not going to pursue it here. >> >> Right. You want to know how much I personally cross compile ? Zero. When > I was toying around with compiling my own kernel was about the only time. > At one point I did setup the Linaro cross tool chain, with code::blocks( > IDE ) on Windows and got that working. But IMHO time is much better spent > learning how to compile natively, from the command line. Because that > information can be used anywhere. Knowing your tool chain from the command > line is a must in my opinion. After that, learning a build tool such as > make is a must too. Quite honestly though, I hardly ever even use make. > Most of my projects are modular in nature, and small applications that > communicate with each other through files. Or other means like mqtt > outbound to a server somewhere. So basically my whole process starts with > writing the code then . . . $ gcc -Wall <source_file> > <target_executable_file> > > Keeping things modular and small makes life for me much easier . . .Not to > be confused with kernel modules of course ;) > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORpGvq6gjkBhYYKuWBmEJynSUOBt%2BGFgpnHhZ5UA0jSL%2BA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
