Quoth Bob Grimes: > I'm still hoping someone knows the magic I'm missing. I can't believe > nobody uses C++ under uClinux!
Well, I do, but I'm using a much older toolchain (I don't have ucfront, for example). And I'm not using -msep-data or -move-rodata. And I'm not using STLport :) Bear in mind that there's a fairly hefty code size penalty in using C++ (at least with gcc), which is possibly why it's not all that common in embedded development. (One issue I came across is that any code in your constructors can be duplicated in the resulting image up to three times for no readily apparent reason. So try to avoid large constructors!) > > ucfront-g++ m68k-elf-g++ -m5307 -DCONFIG_COLDFIRE > > -Wl,--fatal-warnings -Wl,-elf2flt -Wl,-move-rodata > > -msep-data -o fpgatest fpgatest.o libsrc/QSPIManager.o You're not specifying any libraries in there. At minimum you'll probably need -lsupc++; if you're using any STL then you'll need -lstdc++ as well. If you're doing something esoteric you might need -lgcc too, though that's unusual. The library order I normally use is: - custom libraries - -lstdc++ - -lsupc++ - -lm (if needed) - -lc (if needed) - -lgcc (if needed) Don't know if that's "correct", but it seems to work ok for me. _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
