# Porting Linux application to OpenAt

**URL:** <https://forum.sierrawireless.com/t/porting-linux-application-to-openat/7410>\
**Category:** Forum and Source related topics\
**Created:** [August 26, 2014, 11:24am UTC](https://forum.sierrawireless.com/t/porting-linux-application-to-openat/7410 "2014-08-26T11:24:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ubiqsens](https://avatars.discourse-cdn.com/v4/letter/u/dc4da7/32.png) [@ubiqsens](https://forum.sierrawireless.com/u/ubiqsens)\
**Post date:** [August 26, 2014, 11:24am UTC](https://forum.sierrawireless.com/t/porting-linux-application-to-openat/7410/1 "2014-08-26T11:24:19Z")

</div>

How an application which is been written in Linux embedded C can be ported for OpenAt. The application which we are working in Linux will use socket connections, api’s like REST, MOSQUITTO, LIBXMl2, libmodbus. Will all these libraries supported in OpenAt… ? and what is the alternative library for LIBC in OpenAt ?

---

<div class="post-metadata">

**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\
**Post date:** [August 26, 2014, 11:45am UTC](https://forum.sierrawireless.com/t/porting-linux-application-to-openat/7410/2 "2014-08-26T11:45:20Z")

</div>

Hmm… The nature of Open-AT requires a pretty specific approach to the design & structure of the app.

It’s about structure & approach - not just a list of APIs & libraries

> [@ubiqsens](#):
>
> How an application which is been written in Linux embedded C can be ported for OpenAt.

I don’t think there’s a general answer to that.

> [@](#):
>
> api’s like REST

REST isn’t an API.