> > *Since debugging and testing may also require more resources than are > available on the BeagleBone Black, cross-compilation can be less involved > and less prone to errors than native compilation.* >
This is incorrect. Cross compiling anything introduces added complexity, and thus is more prone to errors. The main problem with compiling natively is the time it takes for the beaglebone hardware to finish compiling from source. Another problem is the minimal amount of RAM on the system, which can be mitigated *some* by using a USB hard drive, as a swap drive. Anyway, I think I know what you're saying. So know that when compiling "natively" you're not limited to using a beaglebone only. "Natively" in this context would mean anything that can run, or is running the same OS, using the same ABI. Which in this case the ABI is armhf. In other words . . . most / all armv7 systems. Such as the rPI 2, wanderboard, Beagleboard X15, etc. Can be made to natively compile a binary for the Beaglebone black. This works great, but does take some time to setup perhaps, and does cost additional monies( to purchase another board ). Additionally. I personally write C applications in x86 / i386 a lot. These applications will also 99% of the time directly port to an ARM system with nothing more than copying, and compiling the source to / on that system. C is a true compiled language, where Python, and R( as far as I know ), are byte code / interpreted languages. The point here is that if C can be used in this manner, surely Python, and R can too. What does this mean ? This means that once you have a run-time working on a platform, for an interpreted language. Code written on one system should run just fine on another. Assuming there are no major version barriers interfering. As mentioned above by Dennis. Debian, regardless of ABI is going to have a Python interpreter period. As Python, C, and ruby are all needed in order to build, install and otherwise setup a new Debian( and very probably any Linux system ). So this means you already have a Python run-time available at minimum through the APT package manager. Probably R too but let's have a look . . . googling "debian R runtime" https://packages.debian.org/wheezy/r-base-core william@beaglebone:~$ *apt-cache search r-base-core* r-base-core - GNU R core of statistical computation and graphics system r-base-core-dbg - GNU R debug symbols for statistical comp. language and environment So you need to cross compile what / why ? On Tue, Feb 16, 2016 at 10:43 AM, <[email protected]> wrote: > Thank you for replying. > > BBB has limited resources to make build and install R packages (R-base and > some ML packages, or any other packages for that matter). Also, I would > like to test the build before actually porting the binaries to BBB. Since > debugging and testing may also require more resources than are available on > the BeagleBone Black, cross-compilation can be less involved and less prone > to errors than native compilation. > > -- > 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.
