Dusan Cervenka
Dusan Cervenka
Hi @sujanpepolla79 , we are not authors of this code. This come from community. We don't have ability to fix it by ourself. Could you create PR with bugfix?
Hi @akgalp , all transport layers are usable. But on Linux system tests only tcp can be used to verify eRPC is working correctly. But you can use it in...
It looks like github has many option for automization: 
Hi i am not right now sure. But maybe it is possible when the third command is IN type. Theoretically we can support that in the future (something similar to...
Hi @darwyy https://github.com/EmbeddedRPC/erpc/wiki/Porting-Guide https://github.com/EmbeddedRPC/erpc/wiki/Getting-Started Official doc is for previous version. For current version released recently it is currently on branches. But it si similar allthought initialization parameters or file names...
Hi @tmordeko Just this so far and tests: https://github.com/EmbeddedRPC/erpc/pull/392/files
Any transport supported transport can be used. Not supported transport can be added trough PR.
Hi @amgross, there is no examples with two clients directly. Just example how to init client with new code. If you init two clients and everything in that init is...
Yes you are correct. One server is currently serving request on one transport layer, so i would said that depends on transport layer.
I created this issue related mac build; https://github.com/EmbeddedRPC/erpc/issues/408