Run in different arch machine

[badaix]

Run in different arch machine

[maosuyun2009]

I have know about my problem, first problem is because of different platform have different byte order, maybe should to change byte order in different platform.
But I'm still curious about my second problem, In my mips board, I have to change stream.write(reinterpret_cast<const char *>(&request), sizeof(uint16_t)) to
stream.write(reinterpret_cast<const char *>(&request), sizeof(uint32_t)). so snapserver can receive requestMsg.request == kServerSettings.

[badaix]

On stackoverflow they say that an enum has the size of an int (with arch default size). So it seems to be a bad idea to do the seralization/deserialization the way it's done in Snapcast.
BTW: it was a design decision to do serialization "manually" because there a not too many different messages. In the beginning I was afraid that the day will come where someone has a system with different byte order..
What kind of MIPS board do you have? Did you solve the byte order problem?

[maosuyun2009]

@badaix I haven't solved the byte order problem, My MIPS board is atheros AR9331, But I have successful run snapserver and snapclient in my 3 mips board, It's work fine

[badaix]

@maosuyun2009 can you give me a hint how to build for MIPS?
I have an idle TP-Link TL-WR1043ND router with OpenWrt Chaos Calmer firmware installed. I would really like to have this router running as a snapclient.
Is the cross-compiler the way to go or do I have to create a package.mk? Or maybe both?

[maosuyun2009]

@badaix I alsa build snapcast with openwrt, I just create a package.mk and build to a ipk package

[badaix]

@maosuyun2009 can you share the package.mk script? 😃

[maosuyun2009]

@badaix I don't know how send package.mk to you, so i new a repository, this repository is full package contain old snapcast code.
https://github.com/maosuyun2009/snapcast-for-openwrt.git

[badaix]

thanks @maosuyun2009 👍

[badaix]

Added support for OpenWrt in v0.6.0