Where is .so after build in NI Eclipse 2017

[JacobRiley77]

After building my project I cannot find the .so that should have been made or if it has been made. I was using this guide, (Archived: Getting Started with C/C++ Development Tools for NI Linux Real-Time, Eclipse Edition - NI) but it is for an executable. Does anyone have a better link for making an .so in eclipse or can guide me how?

[ZYOng]

For Eclipse: Archived: Creating Shared Library For LabVIEW Real-Time or VeriStand on NI Linux RT Target

You should consider using the latest guide of Visual Studio Code. See Getting Started with C/C++ Development for NI Linux Real-Time

[JacobRiley77]

I will look at the link, you replied to my other post about using vscode but I am still having an error with calling the vscode-made .so on my cRIO.

[JacobRiley77]

The first link worked for me. I do not like NI Eclipse's menu layout at all, causing it to be a little troublesome, but the .so file worked as it should have in LabVIEW and DOES work on the cRIO. It could have possibly been a compiler issue while I was using Visual Studio Code, the guide shows a different compiler being used as the one in the NI Eclipse guide. Thanks for the links.

[ZYOng]

---

@JacobRiley77 wrote:

 It could have possibly been a compiler issue while I was using Visual Studio Code, the guide shows a different compiler being used as the one in the NI Eclipse guide. Thanks for the links.

---

Both Eclipse and visual studio code are using the same compiler. Just different versions.

Eclipse: 

[JacobRiley77]

I would like to use vscode in the future to create .so. I am using toolchain version 17.0 in both. Visual Studio Code still does not work for me.

[JacobRiley77]

This is my config for vscode. The intellisense automatically updates to linux-gcc-x64. I cannot generate a .so that works in the cRIO. It does work on Windows.

[ZYOng · Accepted solution]

I have attached the visual studio code and LabVIEW project I created following the guide. I am using compiler version 17.0 as well. The project is running well on a Linux RT virtual machine.

[JacobRiley77]

I have found out that the generated files that my CMake and Ninja had used the path for the wrong compiler such as cmake.check_cache and such. Your files worked fine considering the paths were correct.