is libavtp posix complaint and porting it to qnx

[satishkrishna687]

Hi all, so I'm working on project to port libavtp to my qnx setup, as I'm new to this domain I would like some things to be clarified.

1. First Is libavtp POSIX-compliant?

2. Can libavtp be ported to QNX?
   In my project, I am considering using QNX as the operating system. I would like to know if libavtp can be successfully ported to QNX without any major obstacles.

3. Assuming libavtp can be ported to QNX, I would like to understand if there are any specific modifications or adaptations that need to be made. Any advice on the necessary changes or potential challenges would be invaluable in ensuring a smooth integration.

All I could find about libavtp for some presentation slides on the website of anyone could direct me to good documentation on this answers all my above questions that would be of great help. Thank you

[edersondisouza]

Hi,

About POSIX compliance, I don't think so. We use "endian.h", which AFAIR, isn't part of C or posix standard, it's a glibc/some BSD flavour thing.
About QNX, I'm not really familiar with it, but I don't see why it couldn't be done - if the "endian" functions are an issue, there should be workarounds.
I'd suggest to just play with it and figure out what happens =D

[gryadiki]

Hi all, so I'm working on project to port libavtp to my qnx setup, as I'm new to this domain I would like some things to be clarified.

1. First Is libavtp POSIX-compliant?
2. Can libavtp be ported to QNX?
   In my project, I am considering using QNX as the operating system. I would like to know if libavtp can be successfully ported to QNX without any major obstacles.
3. Assuming libavtp can be ported to QNX, I would like to understand if there are any specific modifications or adaptations that need to be made. Any advice on the necessary changes or potential challenges would be invaluable in ensuring a smooth integration.

All I could find about libavtp for some presentation slides on the website of anyone could direct me to good documentation on this answers all my above questions that would be of great help. Thank you

I am also currently working on a project to port libavtp to QNX, and I would appreciate some guidance and feedback from if you have experience with this.

A few key questions I have are:

Is libavtp fully POSIX-compliant, and does it have any known issues or dependencies that may cause challenges when porting to a POSIX-compliant operating system like QNX?

Has anyone successfully ported libavtp to QNX before? If so, what were the major obstacles (if any), and were there specific modifications or patches required?

Are there any QNX-specific adaptations needed for:

Networking stack support for AVB (Audio Video Bridging)?
Timing and synchronization requirements, especially for precise timestamping?
Threading or real-time scheduling to ensure compatibility with QNX's real-time features?
Any advice on handling potential challenges, necessary changes, or good documentation on this topic would be greatly appreciated!

Thanks in advance!

[zeerd]

endian.h is not a problem. QNX has all the interfaces libavtp using. only challenge is found the right header file and replace it.
examples has a problem of argp.h, which is not a part of QNX.
And about Networking stack, you might need BPF.