Using Perforce

In RHv5, I've moved from WinHelp to HTMLHelp. Since there's a
whole lot more source files, I wanted to link RH to Perforce to
automatically use source control.
I set up the Perforce within RH and added the project files.
That seemed to work fine.
Now when I open the project, it looks like RH is creating a
temporary file that is not in the project folder structure and
giving the following error.
Path 'c:\Documents and Settings\thinds\Local
Settings\Temp\pv129.htm' is not under client's root 'C:\dev'.
I have to click through related or repeated messages 11
times, so it's pretty annoying. Then when I try to compile, I get
the following error:
Path 'c:\Documents and Settings\thinds\Local
Settings\Temp\Tmp22035.chm' is not under client's root 'C:\dev'.
Can someone tell me what I'm doing wrong?
Thanks for your help,
- Tom

There is an article about using LabVIEW and Perforce located at http://zone.ni.com/devzone/conceptd.nsf/webmain/69EA27204D24F78586256E2400773ABE?opendocument
Hope that helps.
George M
National Instruments

Similar Messages

How do I use Perforce Source Control on a substituted drive

Hello all,
I am wrestling my way through using perforce as an integrated source control package in Labview.
The path has many potholes but seems possible.
My latest challenge:
Substituted Paths.
In a professional source control environment there are many users with many views/workspaces and it is good proactice for each one to have a unique name [user][machine][branchname][myprojectstructure]
Labview is notorious for requiring fixed, absolute paths due to the way .vi's remember their callers, my previous practice using IBM/Rational clearcase was to substitue ("subst B: ." ) the project root [myprojectstructure] to another drive, say B: for example. This makes Labview is happy as the paths are now fixed, the developer is happy as they don't have to check out a miriad of files.
This practice is widespread in the embedded software development world and isn't exactly innovative.
Perforce
Clearcase integrated into Labview works seamlessly, you just point the path to the substituted drive and all is well.
Perforce, not so much.
The setup options within labview whilst being intuitive and easy to use, don't appear allow this method.
Does anyone know how to do the equivalent in Perforce?
Thanks in advance,
Tim L.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Thanks John,
I will see if this works
I hadn't thought about substituting the drive first and then populating the workspace.
I can see that this implimentation requires discipline,
There is a significant danger of refreshing the wrong workspace and trashing modified files.
Tim L.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Can't use Perforce with Workshop

Greetings,
I configured perforce version 2004.2 in workshop 8.1.3. While perforce native commands work properly in the command line window, they don't in the worksho environment. For instance, right clicking a component in workshop ans selecting Perforce->Status displays:
Problem exec'ing P4 command: java.io.IOException: CreateProcess: p4 -p1666 -unicolas -cssn -Pcalifornia fstat C:\apps\workshop\ssn\SafeSeaNetWeb\net\dgtren\euAdmin\ssn\domain\PortNotification.java error=2
but the same command, ie
p4 -p1666 -unicolas -cssn -Pcalifornia fstat C:\apps\workshop\ssn\SafeSeaNetWeb\net\dgtren\euAdmin\ssn\domain\PortNotification.java
works properly when typed in the command line window.
Did I miss something ?
Kind regards,
Nicolas

Since this was posted back in January I'm sure you have found the solution to this..but just wanted to post it for any others that run across this error.
Make sure that the p4 command line client is installed on your machine and is in your PATH.

Anyone using source control AND cloud sharing?

Hi. I'm curious if anyone has any experience or tips to share about a RoboHelp environment that uses BOTH source control and cloud sharing.
My company uses perforce. I'm purchasing a couple copies of TCS5, one for me in California, one for writer colleague in Europe. I'd like to use Perforce for version control/backup, but use Dropbox for RH asset sharing and sync. Is this workabout? I'm guessing that the Dropbox/sync mechnism won't work if one or both of us has not checked out a file that needs to be (automatically via sync) updated. ("Not checked out" = file is in read only state.)
If RH automatically checks files in/out of perforce in order to complete a cloudshare sync, that would be most cool!
Thanks in advance for your ideas!
-Kurt

Hi Kurt
Have you tried the scenario with RH 11?
It should automatically check-out the file or should prompt for it based on the settings Tools -> Options -> Version Control
I tried with Robo Source Control and SharePoint. And it is working for me. Check-in has to be done mannually.
Please try and let us know the result.
Thanks

Diffing Files in LabVIEW with Perforce?

I've read the sections of articles about doing a graphical difference in LabVIEW with Perforce here: http://zone.ni.com/devzone/cda/tut/p/id/4631#toc4 and here: http://decibel.ni.com/content/docs/DOC-1681#Graphical_Differencing, but I still can't get it to work!
When I right click on a VI from the Project Explorer that is checked out and select Show Differences... Perforce complains that it doesn't know how to do the diff on the files. I assume this is because I haven't told Perforce about the LabVIEW Diff features or the .vi file extension types. How do I this? Is there an article I missed somewhere that describes this step by step?
Edit: I forgot to mention, how do I use the Compare VIs tool in Tools -> Compare -> Compare VIs? When I do this it bring up a dialog in which the first field is the VI I have open. The second field is blank, and that is the VI that I would compare the VI open to. However, since I am using Perforce, the previous file revision are in Perforce. How do I tell this dialog to compare it to a file that is in Perforce?
Thanks in advance!

In the LabVIEW help there's a LVCompare.exe topic; under that, look at "configuring source control with." Following the directions there will allow you to show differences directly from Perforce. However, within LabVIEW, this shouldn't be necessary -at least, it's always worked "right out of the box" for me with no further configuration. Which of the two LabVIEW Perforce clients are you using? You may need to use the command line version in order for differencing to work properly.
Compare VIs does not work the way you seem to expect for VIs in source control. It simply compares any two VIs loaded in memory. To compare with the latest version from Perforce, use Tools -> Source Control -> Show Differences. If you want to compare something other than your current version versus the most recent revision in Perforce, you'll need to execute the diff from within Perforce.

LVcompare and Perforce

Hello,
I have a problem similar to this one, using LabVIEW and Perforce.
My problem is slighly different. I use LabVIEW 2012 f5 and Perforce 2012.1
I want to use LVCompare from LV environnement.
The compare tool works well inside LV, when using two VIs with different names.
My problem is that when I want to compare 2 versions of the same VI, using Perforce, LVCompare launches and everything is blocked. I have to kill tasks both for LVCompare and LabVIEW.
Any suggestion for that problem ?
with many thanks
Philippe
Pièces jointes :
LV compare.png ‏77 KB

HI Philippe,
First of all, which LabVIEW Perforce clients are you using? The command line version ?
Are you sure to call the LVCompare.exe within Perforce for diff and not another one ?
Moreover these are steps you can use and check:
1. Launch Perforce client (P4V ?)
2. Edit -> Preferences
3. Select the Diff tab
4. Click Add
o If you already had a tool (LVDiff) setup to diff VIs, select that entry and Click Edit
5. Enter this data in the pop-up dialog
o Extension: .vi
o Application:
§ C:\Program Files\National Instruments\Shared\LabVIEW Compare\LVCompare.exe (32bit)
§ C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare\LVCompare.exe (64bit)
o Argument: %1 %2 -nofp -nobdcosm -nobdpos
6. Save
7. Repeat for .ctl, .vit, and other LV file types
o NOTE1: Consider using the '-nofppos' option instead of the '-nofp' especially for .ctl's. Otherwise LV Compare will not show any differences for controls/typedefs.
o NOTE2: Do not add .lvproj, .lvlib or .lvclass to the list, as those files are XML files that LV Compare can not handle (as of LV 2012) and are simple to diff with text compare.
These command line options listed above will:
· use the current LV version for the diff (since I did not list a LV version to use)
· does not compare the front panels (-nofp)
· does not compare front panel objects' position/size (-nofppos)
· does not compare the appearance of block diagram objects (-nobdcosm)
· does not compare size or position of lock diagram objects (-nobdpos)
See the full LV help for a complete list of all command line options.
Hope it could help !
Antonin G. Associated LabVIEW Developper
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Communauté francophone des développeurs LabVIEW et des enseignants en STI2D
Si vous souhaitez partage...

LabView and Perforce renaming a vi in your project

Hi All
Im using Perforce as our SCC and I've integrated it into LabVIEW, all OK but I have a concern that hopefully someone can shed some light on.
If you use Perforce you will be awars that if you check out a directory then from File Explorer delete or rename a file then Perforce is not forgiving and will not continue untill you give it back the file that you checked out. Fair enough and to do such opperations you should work within the Perforce Client.
However I would have expected that when you tell labVIEW that perforce id your SCC and within the Project manager you rename a file for the obvious reason that you want vi and control linkages to remap, that LabVIEW would execute the correct series of commands to perforce to tell it that the file has been renamed. Because when you go to check in your project folder Perforce wants that original file.
Has anyone experienced this and knows a workarround?
Cheers
Kurt

Kurt_Cochlear wrote:
Hi All
Im using Perforce as our SCC and I've integrated it into LabVIEW, all OK but I have a concern that hopefully someone can shed some light on.
If you use Perforce you will be awars that if you check out a directory then from File Explorer delete or rename a file then Perforce is not forgiving and will not continue untill you give it back the file that you checked out. Fair enough and to do such opperations you should work within the Perforce Client.
However I would have expected that when you tell labVIEW that perforce id your SCC and within the Project manager you rename a file for the obvious reason that you want vi and control linkages to remap, that LabVIEW would execute the correct series of commands to perforce to tell it that the file has been renamed. Because when you go to check in your project folder Perforce wants that original file.
Has anyone experienced this and knows a workarround?
Cheers
Kurt
I use SVN and you can re-link the files. With the Tortoise front end it's as easy as selecting both files and saying that it was renamed. That way you keep the history intact. Maybe you can do something to that effect?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

No connection to perforce SCC in application

Hi,
in my project i am using Perforce as source code control provider. Currently i can check-out and check-in VIs in the projectexplorer. Also i can check-out and check-in different files programmatically with the Labview SCC-VIs. This works fine in Development mode but in my built application an error occures: The Open SCC Proveder.vi returns -2983 (No access to source control provider).
I already copied the SCC Tokens SCCConfigData, SCCProviderName, SCCProviderLocation from the Labview.ini to my project.ini.
Michael

I would start by including Either the P4CMD directory "....vi.lib\SourcControl\Providers\P4CMD"
or the WinCI directory "....vi.lib\SourcControl\Providers\WinCI"
depending on which interface you have your SCC configuration set up to. The SCC vis make dynamic calls to the various providers required to
support the different SCC platforms and thus need the specific provider
files specified discretely. The Report Generation Toolkit works very
similarly to this.
This will most likely solve the issue.

Perforce Integration Headaches

Hi all,
This is a cross post from LAVA.
I have recently installed Perforce on our server
(P42008.2) and Perforce Client (P4V/NTX86/2008.2/188141) on our
developers PCs (WinXP SP3, LV Full Dev Suite).
I then configured LabVIEW SCC, telling it to use
Perforce Command Line and told LabVIEW where to find the server etc. I
then moved an existing LabVIEW Project to my workspace folder and opend
it in LV, right clicked on the top level VI and selected "Add to Source
Control...". A window popped up showing me all the dependencies of the
top level VI and clicking OK displayed a window telling me that each
file had been added to the depot as " - opened for add". I click OK and
LabVIEW does not indicate the files are in SCC.
I then switch to the
P4V client window and submit the changelist (adding the VI and it's
dependants to Perforce). I repeat this process for the .lvproj file and
voila!, the project is in Perforce. Back in LabVIEW however there is no
indication the project has been added to SCC (no check in/check out
glyphs on project icons) and when I right click on the project, I only
have the option to "Add to Source Control..." again????. Of course
trying to add the project to SCC again thows up erros about existing
files etc.
What am I doing wrong??
PS I have tried this with LabVIEW 8.5.1 and 8.6.

Hi,
Did you configure Preforce and SCC as instructed in these two articles?
http://zone.ni.com/devzone/cda/tut/p/id/4631
http://digital.ni.com/public.nsf/allkb/B371AC6D6CCE335E86256CE2004A5853?OpenDocument

Perforce SCC and Labview 8.5

I have been using Perforce with LV for a couple of years now and until recently, all has been ok.
Trouble is I recently upgraded the PC that was running my SCC and upgraded my client installations, well I'm assuming thats part of the problem anyway.
On my client PC, I have the perforce root set to a folder on my D drive. Now, everytime I open LV 8.5, open a library file or code that uses a library file I get an error from Perforce telling me that path xxx.vi is not under client root folder.
Well, of course it isn't - it never was before, why does it need to be now?
when it's only 1 message it's an annoyance. when it's 20 or 30 that i need to acknowledge before I can get on it's a right royal pain the arse.
This behaviour is not seen on LV7, 7.1, 8.0 but it is on LV 8.2
Any ideas on how to resolve this? other than moving my client root folder of course, which I don't want to do.
Ta
Matt

Ooop - pressed the wrong button.
I am using client version P4SCC/NTX86/2005.1/85663 and server version 2007.3/143793. SCC provider is set to Perforce and yes, all the versions of labview I have tried this with are on the same client PC.
I haven't tried the P4 command line from my client PC - I'll give that a go and report back.
My initial thought given that it affects both 8.2 and 8.5 is that it has something to do with the way LV is interfacing with Perforce, but beyond that I'm at a loss. For example both 8.2 and 8.5 request and are given a 12 houre perforce ticket, which none of the other versions do (login expiration dialog under SCC options --> advanced, tab connection.)
M

The UML Package model could not be resolved - SOLVED

I am using Perforce with JDeveloper 10.1.3.2.0. I have imported a project into Perforce on one machine, then 'p4 sync -f' on another machine. I then created a new application on this machine and added the projects to it. Now, when I try to open a diagram in package 'model', it gives this message:
The UML Package model could not be resolved
The element may have been moved or deleted from the file system, or the Model path, source path or classpath may be incomplete. This error can also occur when the element was found, but errors in its definition prevented it from being loaded. Examine the error stack for further information on the exact cause.
It also looks as if certain other files in the other projects are missing - it looks like a problem with the Perforce extension to me, or is it because I do it wrong?
Message was edited by:
jandersen

It gets stranger and stranger, I think.
As I told, I imported the project into Perforce, to a directory called /dtl/admintools, and found that I could still open all files - I did find that one file was missing (/dtl/adminstools/sysadm/SysAdm.jws), so I added it to Perforce. I then removed everything under /dtl/admintools and sync-ed it out from Perforce on the same machine - it still worked fine.
I then went to my home computer and did the same thing (over a VPN) and checked that I had received all the files, which I had. I then tried to open /dtl/admintools/sysadm/Model/model/model/SysAdmDiagram.oxd_bc4j, which contains entity- and view objects - this give the error message. I can see all the objects listed in the structure list, but if I try to open any of them, I get the same message. There are no error messages other than the one that pops up.
Both my workplace computer and my home one are AMD 64 machines running Gentoo Linux and it's the same version of JDeveloper too.

Software Configuation Management for Labview

We are a small medical device company that uses labview to develop our software applications. We would to implement a software configuration management package to control our source code. Does anyone have a recommendation for a good package to use with labview? I have used Perforce previously and am looking that way again. Thanks.

The following KB answers that question. You can also do a search on 'Source Code Control' on our website to find more about this.
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

TestStand 4.0 Types

We have a large TestStand project with multiple development PCs and developers. We are using Perforce to source control and share our work. We have created some custom type files which are in the Teststand\Components\User\TypePalettes directory which we have put under source control. This has worked well in the past.
We recently upgraded to TestStand 4.0. Subsequently, we decided to customize the order of the Step Types in the insertion palette. After customizing the Step Type Menu, all of the type files under NI's directory and the User directory in the Type Palette are starred indicating that they all have changes to be saved.
If we save all the type files on that PC and then check in our custom type files under \User, we would like to be able to go to our other development PCs and get the latest revision of the type palettes in the \User directory and have those other PCs show the new step type menu structure. That does not happen unless we also copy the \NI\TypePalettes\NI_Types.ini file to the other PCs.
We have three workarounds, all of which have negative consequences:
1) Leave NI_Types.ini out of source control and manually copy it to the \NI directory of each development PC every time we change the Step Type Menu.
The bad: prone to error if a copy is not done on one station or if the wrong version of NI_Types is copied.
2) Copy NI_Types.ini from the \NI to the \User add add it to source control. This allows us to automatically update our Step Type Menus across all the dev PCs just by getting the latest revision of \User from Perforce.
The bad: TestStand now shows two versions of NI_Types in the Type Palette, one from \NI and one from \User. We had hoped that once TestStand found NI_types.ini in \User, it would no longer use the one in \NI, as happens with other files that are copied from \NI to \User such as the sequential model.
3) Do 2) and additionally manually delete NI_types.ini from \NI on each dev PC.
The bad: It's a manual operation that will have to be remembered for each existing dev PC and any new ones we buy. Then when we upgrade to a future TestStand version, we're guessing that NI_Types.ini will again show up in \NI so we'll have to manually delete it on each PC again.
Questions
1) Is it a bug that a TestStand modification such as editing the Step Type Menu makes changes to files outside of \User? It does create problems for us. We thought the whole point of \User was to avoid these types of issues.
2) Is there a better workaround than what we have come up with?
Thanks,
Hans

For anyone that is looking for the answer to this post, it can be found here.
Pat P.
Software Engineer
National Instruments

Sharing and syncronization TS configuration and components files

Hi,
We have several TestStand development PCs and we are using Perforce to source control and share the work.
We need to share TS configuration file (TestExec.ini, StationGlobals.ini, Users.ini, etc.) and the following components:
SequentialModel.seq, FrontEndCallbacks.seq and CustomStrings.ini.
We work with configuration files, SequentialModel.seq and MyTypes.ini located under our project (not default TS folders).
1. Is it possible to set custom location also for FrontEndCallbacks.seq and CustomStrings.ini? If yes - how, otherwise - how can we share these files without deployment or manual copying?
2. How to synchronize the frequently changed files - MyTypes.ini, TestExec.ini and StationGlobals.ini? The files format is INI (text).
If two users will change the such file and one will submit the changed file, the second user will get conflict. Is there a convenient way to compare two file versions and resolve the conflict instead of using text comparing program (e.g. Beyond Compare)?
Thanks in advance

Hello Berezka,
TestStand checks for the location of FrontEndCallbacks.seq in two different locations:
<TestStand>\Components\User\Callbacks\FrontEnd
and
<TestStand Public>\Components\User\Callbacks\FrontEnd
If you configure a custom public directory (possibly on a network), then I could see files being shared between two development machines. The following article explains how to accomplish this task.
How to Configure a Custom Public Directory for TestStand 4.1 and Later
http://digital.ni.com/public.nsf/allkb/42A0D8B0DCEC64FE8625744F007F3A6D?OpenDocument
And as far as a side by side comparison of two files go, I would use the File Diff/Merge application when it comes to .seq files. This application is located at Start»All Programs»National Instruments»TestStand»Tools»File Diff and Merge. However, I understand we're interested in .ini files. Beyond Compare may be your best bet, but there are other apps I've found such as TortoiseSVN and ExamDiff.
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

Labview opens all VIS in Run mode

LV2013 PDS is opening all VIs in Run Mode. This is a global problem, not specific to one or a specific number of VIs.
If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode. Nothing is set to Run When Opened, nothing is set to be locked without a password.
It's only on this installation; if I take my code to another machine, there's no issue.
I have deleted the labview.INI file, but the behavior repeats itself.
Any ideas?

Jed_Davidow wrote:
SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked. I have also checked out all the filed ahead of time with P4, so LV never sees them locked. The folders themselves are not read-only.
Also, I have created VIs outside of my P4 folder, and I have the same trouble.
Example:
Launch LV: Create a blank VI (comes up in Edit mode).
Save to Desktop (not within P4 control) as test.VI
Close
Open test.VI ---> It's in Run Mode
I have never seen this happen before.
Neither have I
I'll assume a reboot was attempted and did not change anything. I would attempt a repair of LabVIEW from the control panel and another restart.
Jeff

Using Perforce

Similar Messages

Maybe you are looking for