While QNX is not officially supported, the first question should be if the embedded device is using a supported CPU architecture. Currently .NET Core supports x86, x64, ARM32 on ARMv7+ chips (that means no raspberry pi 1 / zero for example) and ARM64 (as of .NET Core 3)

I should have mentioned that. In my case, this is x86. I fully understand that architecture is a bigger question.

I have no knowledge of QNX, but you can give it a try.
You can try to build native components of coreclr on QNX as the first step and see if you can make it work. For the first steps, you'd need at least cmake 2.8.12 or higher, clang 3.6 or higher and make. I would try to start from there and see what the build complains about. Then install missing packages / fix build scripts or source and repeat. I'll be happy to help you understand errors that you couldn't easily decipher.
To try to build, just clone the coreclr repo and run ./build.sh

Great, that is good to hear! I will try to not bother you guys too much.

What is the relation of libuv to ASP.NET Core 3? It looks like it isn't supported on QNX (See here).

It looks like it isn't being used.

I created an MVC app using 2.2.103, published as self-contained, and all I see is this:

-rwxrw-rw- 1 pknopf pknopf  3126440 Dec  7 15:53 libclrjit.so
-rwxrw-rw- 1 pknopf pknopf 10296824 Dec  7 15:54 libcoreclr.so
-rwxrw-rw- 1 pknopf pknopf   718384 Dec  7 15:54 libcoreclrtraceptprovider.so
-rwxrw-rw- 1 pknopf pknopf  1071808 Dec  7 15:54 libdbgshim.so
-rwxrw-rw- 1 pknopf pknopf   692128 Dec  7 17:48 libhostfxr.so
-rwxrw-rw- 1 pknopf pknopf   712624 Dec  7 17:48 libhostpolicy.so
-rwxrw-rw- 1 pknopf pknopf  3942256 Dec  7 15:54 libmscordaccore.so
-rwxrw-rw- 1 pknopf pknopf  2750824 Dec  7 15:54 libmscordbi.so
-rwxrw-rw- 1 pknopf pknopf    88728 Dec  7 15:54 libsosplugin.so
-rwxrw-rw- 1 pknopf pknopf   719864 Dec  7 15:54 libsos.so
-rwxrw-rw- 1 pknopf pknopf    92216 Dec  7 15:54 System.Globalization.Native.so
-rwxrw-rw- 1 pknopf pknopf   768680 Dec  7 16:49 System.IO.Compression.Native.so
-rwxrw-rw- 1 pknopf pknopf    60848 Dec  7 16:48 System.Native.so
-rwxrw-rw- 1 pknopf pknopf    14832 Dec  7 16:48 System.Net.Http.Native.so
-rwxrw-rw- 1 pknopf pknopf    10672 Dec  7 16:48 System.Net.Security.Native.so
-rwxrw-rw- 1 pknopf pknopf   125616 Dec  7 16:48 System.Security.Cryptography.Native.OpenSsl.so

This looks good.

@paulbrittain as of ASP.NET Core 2.1, socket transport (implemented over System.Net.Sockets) replaces the libuv transport as default.

@pauldotknopf Were you able to make it work? I am facing the same requirement here.

@guesshe, my requirements changed, I didn't need it after all.

@pauldotknopf Thanks! Were you able to port cmake and clang to QNX anyways?

I have built coreclr but now I am stuck with how to execute a dll program on qnx. I tried to build dotnet executable but not sure if it is the right path. Any suggestions here would be greatly appreciated. Thanks!

@janvorli Would you please help here? How can I execute a dll program on qnx? Do I need to build dotnet executable?

How can I execute a dll program on qnx?

Maybe you are unfamiliar with clr structure and I can help you about this.

Yes, running dll assembly requires a native executable to launch it, in several possible ways:

1. dotnet command. The one powers every developer side things. May be most complex to build, but solves almost everything.
2. corerun. It's too simple, and is only used for quickly debugging clr itself.
3. The native executable produced by dotnet publish - r (I cannot remember the codename, maybe corehost?) Should be the best choice for embed scenarios that doesn't require developer stuff.

@guesshe

While compiling the coreclr, I'm stuck at the fpsimd_context in the PAL, since the said structure is not available in QNX.
Can you please provide any pointers ?