> > *Finally, although cross-compiling is faster you can of course also just > compile on the beaglebone itself. The native gcc is 4.9.2 in debian > "jessie" (stable) and gcc-5 is available in "stretch".* >
I concur. Stuff like compiling the kernel would be all but out of the question. Wireshark, Qt, and largish projects like this too. Something like Nodejs however, I would consider passable( Only takes about an hour to compile natively ). But for like 95%+ of user written / compiled executables. Natively is more than good enough. For example, I have a CANBus app I'm writing. Compiling on a 4 core 4GB virtual machine compiles the executable instantly. On the BBB it takes a second to compile. Granted the code base is rather small at the moment. Less than 500 lines of C( so far ). I would however recommend using a working directory that is on non flash type media. Such as a NFS or USB hard drive mount. On Mon, Jun 15, 2015 at 9:41 AM, Matthijs van Duin < [email protected]> wrote: > On 15 June 2015 at 06:52, Robert Willy <[email protected]> wrote: > >> I don't know how to get assembly code list file from compiling. > > > I actually used it in my reply to your original post: > > On 14 June 2015 at 12:45, Matthijs van Duin <[email protected]> > wrote: > >> [..] compile it with "arm-linux-gnueabihf-gcc -Og -S -o- foo.c" >> > > The options I use here: > -Og a very mild optimization level (milder even than -O1), most likely > to produce very straightforward assembly output. (Introduced in gcc 4.8) > -S produce assembly output instead of object code > -o - send output to stdout (you can send it to a file instead of course) > > I do suggest you upgrade your rather dated 4.7.x compiler to a more recent > one, either 4.9.x or 5.1.x. Debian "stretch" (testing) and "sid" include a > "gcc-5-arm-linux-gnueabihf" package. > > The distro-independent Linaro toolchains are a useful alternative. They're > good toolchains for various ARM targets, both linux (64-bit) and windows > (32-bit) hosts, and completely standalone (just unpack the archive anywhere > and put its "bin" subdir in your PATH). > > They are a bit annoying to locate in their download area however. I don't > know of a better way to find the most recent version than checking the > directory for each month to see which one contains a > "components/toolchain/binaries/arm-linux-gnueabihf" subdir. Their most > recent version currently seems to be the 2015.02 release > <http://releases.linaro.org/15.02/components/toolchain/binaries/arm-linux-gnueabihf> > (you > only need the gcc download). > > Finally, although cross-compiling is faster you can of course also just > compile on the beaglebone itself. The native gcc is 4.9.2 in debian > "jessie" (stable) and gcc-5 is available in "stretch". > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
