From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Hidden Gems in vi.lib

cancel
Showing results for 
Search instead for 
Did you mean: 

AB_API: Setting destination paths for Linux RT?

I've run into a bit of a problem with the Autobuilder API I'm not sure how to work around.  We anticipate our Linux RT build and deployment process for add-on components to look something like this:

1. Use the AB_API to create source distributions.

2. Create opkg files from the source distribution deployable to remote sites.

3. Create code on the device to use opkg to download and install necessary packages.

The problem I'm running into has to do with Set Destination Path.vi.  This vi uses a path control for the destination path input.  Because the build code runs on a Windows machine, when I try to set a linux style destination path (\home\lvuser\...) it gets converted to a windows format (c:\home\lvuser\...), which generates an error "Destination path contains invalid characters."  That's understandable, as the code is being built under a linux target.  I can use a linux style relative path (home\lvuser\...) (note the missing preceeding back slash) but then the destination path in the build spec isn't set correctly.

How can I set an absolute deployment path for a linux target using the AB_API running on a Windows machine?

EDIT:

When I use c:\home\lvuser\... as the destination path, in the build spec it is showing up as /c/home/lvuser/...

When I user home\lvuser\... as the destination path, in the build spec it is showing up as home/lvuser/...

Neither of these options is correct.  I want the destination path to be /home/lvuser/...

Message was edited by: Daklu

0 Kudos
Message 1 of 3
(7,338 Views)

Try home:\lvuser\...

If that doesn't work, try making the source dist manually on Linux, then use the API to read the destination path on Windows to see how it's stored.

Message 2 of 3
(6,827 Views)

home:\lvuser\... did the trick. 

Thanks Darren!  (I had assumed that syntax was some sort of network access.)

0 Kudos
Message 3 of 3
(6,827 Views)