> So it looks that now, when I run the make command, it starts the > compiling process correctly, but because it tries to execute the binary > files (and it can't, because they are generated for the MIPSEL > architecture and not for my machine's) the compiling stops. The only > binary file generated (after running the commands make and make install) > is soapcpp2 =\ Isn't there a way to disable binary file execution during > gSOAP compiling process? I tried to look at the ./configure command > options but I couldn't find any flag that looks useful to do that. > Because I guess that if I could disable that everything would be ok.
Ah ok, sorry I'm not too familiar with the examples. It sounds like there's some confusion between soapcpp2 being set as a host executable or a target executable. It probably depends on whether you're building the gSOAP library itself (soapcpp2 should be target arch) or whether you're building the examples (soapcpp2 should be host arch.) Probably the easiest way is to figure out how to compile your code independently of gSOAP, so that the make process uses the version of soapcpp2 already installed on your system, instead of compiling its own for the wrong arch. Cheers, Adam.
