Hi Jean-Michel! Fully agree, if a build takes 8 hours, your system isn't the system you should build on, even if it "feels" like a full PC!
However, at the time, I don't have anything better to offer to Barry, seeing that Raspian AFAIK doesn't ship current GNU Radio, and setting up an OE build dives far too deep (all assurements of active OE users aside, I've done quite a few OE builds in my time, and it's almost never trivial once you leave predefined roads). What we're aiming for 3.8 is wide distro adaption, including things like Raspian, that take the burden of trying to build software for these "heavy embedded" devices off the user. I'm in the meantime not aware of a working package for raspbian that'd contain GNU Radio 3.7.13.5 or 3.8-rc2 :( Cheers, Marcus On Wed, 2019-07-31 at 17:41 +0000, jean-michel.fri...@femto-st.fr wrote: > > It took about eight hours total. > > I would hope this list would stop promoting building on the target > embedded system. > > Embedded system development should never, ever, attempt compiling > on the low power target but rather figure out how to cross-compile > from the powerful host for generating binaries targeted to the low > power embedded board using appropriate tools (e.g. buildroot, Yocto > or > OpenEmbedded). > > Unfortunately having an HDMI connector for a display and a USB port > for > the keyboard with a ready-to-use distribution such as Raspbian makes > RPi > users believe that they have a full computer available and forget > proper embedded system development practices as I see daily from most > students. Would anyone consider running gcc on a low-power STM32 or > MSP430 > for compiling the firmware ? > > JM > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
