LabVIEW Real-Time Idea Exchange

About LabVIEW Real-Time Idea Exchange

Have a LabVIEW Real-Time Idea?

  1. Does your idea apply to LabVIEW in general? Get the best feedback by posting it on the original LabVIEW Idea Exchange.
  2. Browse by label or search in the LabVIEW Real-Time Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  3. If your idea has not been submitted click New Idea to submit a product idea to the LabVIEW Real-Time Idea Exchange. Be sure to submit a separate post for each idea.
  4. Watch as the community gives your idea kudos and adds their input.
  5. As NI R&D considers the idea, they will change the idea status.
  6. Give kudos to other ideas that you would like to see in a future version of LabVIEW Real-Time!
Showing results for 
Search instead for 
Did you mean: 
Chris V

Support for Building VxWorks Shared Libraries (*.out files)

Status: New

The best thing about Pharlap is that it will run dll's like Windows.


Making shared libraries for VxWorks (*.out files) is quite an arduous process if you don't have Wind River software.  The GNU toolchain, that used to be the free alternative, does not work on Windows Vista or 7, leaving those of use who have chosen to upgrade out of luck.


It would be great is LabVIEW could provide a way to compile *.out files from the Application Builder and thereby provide more complete support for development on the CompactRIO platform.

Applications Engineer
National Instruments
1 Comment
Active Participant

You noted that this is painful if you don't have Wind River software.  Is there any problem (other than "it costs money") with using the Wind River tools?  We partner with Wind River specifically for this reason and would definitely encourage anyone who wants to develop shared libraries for VxWorks to use those tools.


That said, if you prefer the raw toolchain without the tools due to the cost, that toolchain should work on Windows 7 (I use it that way).  Have you reported your issues with it to NI support?  If not, can you clarify what is going wrong?  Have you seen the comment posted with the toolchain at about using it under cygwin to resolve a Windows 7 shell incompatibility?