Ok I have build a few kernels OS etc and its pretty painful but doable ( just time consuming sorting out cross compiling ) . The code all seems good and compiles under the right conditions ( even mono) but creating a flexible and easy to use and reuse build environment is troublesome. I mainly want I386 ( pentiumII) - uclinbc with noMMU but later build arm it would be great to get arm tested in an automated nightly build so it stays in step.
I have tried ucLinux dist which seems ok ( got a new board setup under Intel) but under certain conditions I get the crypto FENV header issues and im not sure it's using the right compiler. Tried Build root and got a few issues to do with the rebuilding and math lib errors. Some people suggested using a clean version and an external download and use crosstool-ng as an external lib . Or I can create my own build environment which while annoying and very limiting now seems better in the longer term ( as I eventually I will only use ucLinux + uclibc + mono and most of the apps will become mono apps and hence can just be copied assemblies which will work for any platform . Any advice on this and what other people do ? Do you carefully match tool chain and ucLib versions with buildroot/uclinux ? Do you use old true and tried versions ? Lastly what do you throw in automated builds / source control ? Binaries or just certain config dirs ? _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
