Who cross compile rtptools about rtptools

[janstary]

All of these archs run linux (by definition),
so they can compile natively, which makes this a bit pointless.

In general though, we are interested in platforms that do need to cross-compile.
Please report here if you want to run rtptools on such a platfrom.

[mcd500]

The rtp protocol are used on voice/tele conference machine.
Working at the electronic company would require to have cross-compiling since it can not build natively on the device like polycon and cisco products.

[mcd500]

It is very strange for me for the comment.
"so they can compile natively, which makes this a bit pointless."
while the huge number of engineers have to use cross-compilation for making earnings.

[mcd500]

The products of embedded network device such as voice/tele conference machines tend to use bigendian hardware for the performance of handling network byte order.

[janstary]

Yes, every HW VOIP phone (for example) needs to have a RTP implementation.
And most probably it has been cross-compiled for the machine. And yes, telco engineers
must cross-compile that stuff daily. How does that relate to rtptools specificaly?

But really, if anyone needs to cross-compile rtptools, please report here.

[mcd500]

I did have to cross compile rtptools when I was working for electronic companies.

When prototype boards comes out from hardware department, and the software engineer have to work on the board,
often time what happened was that initial batch did not have any of external network connection such as ethernet or 3G/LTE were not working.
Some time, the board does not have ethernet chip or came out with the chip do not have driver (or changed without notifying software department) or 3G/LTE have not passed the FCC/Telec compliance and can not distribute any radio out of the device even working inside the building (Precious Anechoic chamber is for hardware engineer to pass the compliance as soon as possible).

But software programmer would like to test RTP protocol as soon as possible to meet the deadline.
So easiest to test RTP packets from the software stack was using rtpdump, rtpplay and rtpsend internally in the board using localhost, for at least cheeking the packet confirmation and integrity.

The supporting cross-compilation on the new configure is not high priority but it is worth making it work in the future.

[janstary]

Running rtpdump and rtpplay localy is exactly what I intend to do in make test :-)