> For me it's kind of weird that I have to add that to a file that's > generated during compiling... Shouldn't that include be made > automatically during the compiling process?
Yes it should, this was just a test to see if it worked. Since it worked, it looks like a bug in gSOAP. Probably good if you could report it! > to the top of stdsoap2_cpp.cpp and then run make, besides lots of > other things, it appears this > > > /bin/bash: ../../gsoap/src/soapcpp2: cannot execute binary file > > which for me makes sense, since I'm generating a binary file for the > MIPSEL architecture and not for my computer's architecture. To confirm > that, I've copied that file to the router and tried to run it and it > apparently works fine. I've attached the output of the make command in > the make_output.txt file. That's correct. When you compile gSOAP for MIPS, you get all the libraries and tools in MIPS versions. No doubt you would also compile it for your local architecture if you wanted to use the tools on the machine you're doing the compiling on (which is probably true for soapcpp2.) I imagine you would use --prefix to install the MIPS versions in a different folder, along with all your other MIPS libraries (say /home/mipsroot/lib/). You would then use your local arch version of soapcpp2 to generate the source files for your application, cross compile your app for MIPS and then install it into the same folder as all the other MIPS files (e.g. /home/mipsroot/bin/). Then that MIPS folder would be packaged up and installed on the router, so the lib files go in /lib and the bin files go in /bin. Cheers, Adam.
