Hi [mbm] and anybody else would made OpenWRT already that nice,
I was just about to create a mobilemesh package (http://www.mitre.org/work/tech_transfer/mobilemesh/) for b4-pre. However, mobilemesh is c++ and therefore needs gcc++ as well as the libstdc++. Whereas I (a "dump" developer) am able to compile and package mobilemesh, I am, however, not able to compile the gcc++ and libstdc++ . Unfortunately :oops:
I tried to compile gcc++ and the libstdc++ by setting "INSTALL_LIBSTDCPP:=true" in the Makefile, but this did not work, since this statement seemed to be ignored by the make process. Anyway..
Even if I could compile it, I would then probably include the libstdc++ within the mobilemesh-package. Other c++ programs will maybe also provide the libs they need within their specific package.
I would like to suggest the following:
The "make" does not only build the openwrt-code.bin and a toolchain for c-programs, but builds a _real_ toolchain with:
* gcc++ and libstdc++
* whatever libs are also needed quite frequently
The libs in this toolchain (or a buildroot, if you prefer) are then provided in form of packages for the Linksys WRT54G. This way all package maintainers use the same version of a library and do only have to make their specific library make depend on that provided lib.
Just a suggestion, but I think, such a automatically built environment for package maintainers would certainly speed up the package developement.