4 ms·
In the 2006-2009 timeframe, I worked at a company where I replaced this unwieldy monstrosity with a from-scratch distro + toolchain. It was an incremental appr
by kazinator 3y ago
In the 2006-2009 timeframe, I worked at a company where I replaced this unwieldy monstrosity with a from-scratch distro + toolchain.
It was an incremental approach. For a while, we kept running Wind River, but I replaced glibc with one I built completely not using anything from Wind River, and eventually all packages, config files and scripts in rootfs, and the kernel, until there was nothing left of Wind River.
At that time, those WR clowns hadn't figured out how to build a cross-compiled Bash that had job control. Everyone was relieved when they could use Ctrl-Z suspend and fg/bg on the target with our home spun package.
Funny thing is, that startup spent about a year looking for someone to do all this, while I worked on some C++ application stuff. Then they realized the person works there already.
Didn't Wind River have some awful build process that stitched together files from disparate fragments? Or something? My memories are fuzzy.
On this project, I had the idea of doing all patching of packages with Quilt. Yocto does that now. Years later when I had to add some patch to a Yocto package, I went into the build directory and, oh, lookie, I already know how to do this with my eyes closed.
I made ever single package cleanly cross-compile for MIPS: no Qemu on the build machine. A co-op student came on board, who was into Macs; he pretty easily got everything to build under MacOS.