Hi again,
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.
Again, thanks for the time spent with this and thanks for helping me.
Cheers,
Nuno
Adam Nielsen wrote:
>
>
> > 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.
>
>
