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...

Similar Messages

  • Version control (lvcompare and lvmerge) for projects, classes and libs?

    Hi everyone
    Version control for classes, projects and libs (not just a plain .vi) - can it be done with lvcompare and lvmerge?
    I've tried a simple "LVCompare.exe project1.lvproj project2.lvproj" and it only returns an error (lvcompare.exe vi1.vi vi2.vi works). So this is maybe a dead end.
    How do you guys version control more complex projects? E.g. projects which use classes, libs, labview projects (.lvproj)?
    Best regards
    Jonascj

    Thank you for your reply. You are right, .lvclass, .lvproj and .lvlib are all just xml files - I've just figured that out my self when I accidentally called GIT's default diff on a lvclass
    I've also just spoken to National Instruments. The person I spoke to (from the one of the danish offices) told me that no tools exist at this time (2013-04-08) which will compare those LabView file types, but that there was an internal (National Instruments themselves)  feature request for such tools.
    He also told me another interesting thing which I did not know. The lvcompare.exe (located in National Instruments/Shared/LabVIEW Compare/ on Windows) is actually the not developed by National Instruments, but is either a "fork" of LVDiff (http://meta-diff.sourceforge.net/) or LVDiff renamed. So one could simply obtain the source code from http://meta-diff.sourceforge.net/ (at the bottom of the page "Win32 binary w/source") and add a few property nodes to do comparision of lvclass attributes etc.

  • XControl Properties and Perforce

    I seem to repeatedly have problems checking in XControl read and write properties to my Perforce repositary.
    The Property folder tells me it can't be added because it hasn't been saved and the Read and Write VIs don't give me the opition to add to source control on the right-click menu.....
       Can't add the Property folder
      Can't add the individual files..
    Is this a bug or am I doing things wrong?
    This is making working at home andin the office a real pain as VIs are getting "lost"
    Shane.
    Say hello to my little friend.
    RFC 2323 FHE-Compliant

    Hello Shane,
    from my point of view the message is quite clear, you will find some informations about your next steps in the dialogbox. You have to save the file you want to add to Perforce. But am I right, that this is one of the first things you have done?
    I found some other informations which could help you out with this. First of all, only for assurence the general "How to do":
    Using Source Code Control with LabVIEW and Perforce
    http://zone.ni.com/devzone/cda/tut/p/id/4631
    Another very interesting thing it
    is discussed in a Perforce Bug Release Document (see link below).
    From the Perforce Release Notes:
    Issue Number: 103269
    Clients with upper case letters drive letters in the root no longer fail to connect to the server. (Bug #21582)
    Resolution:
    In the Client Specifications Root Path setting in Perforce, change the drive letter from a capital case to a lower case (Example: change "C:\" to "c:\"). 
    Restart LabVIEW and reopen the project. 
    The "Check In" and "Check Out" items will no longer be grayed out and you should no longer receive the error messages.
    http://www.perforce.com/perforce/doc.061/user/sccpluginnotes.txt
    Hope that helps. Regards,
    Jan Kniewasser | Applications Engineer | Tel.: +49 89 7413130 | Fax: +49 89 7146035

  • 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.

  • Xcode and Perforce

    Has anyone been able to setup XCode to work with a Perforce SCM server? I know that this is supported and can be done, but I have not been able to integrate Perforce into XCode's SCM features. I have installed the P4 command line app and it says that it has authenticated properly. However, when it attempts to list the contents of the repository, the log reads:
    Xcode[18884:203] * NSTask: Task create for path '/usr/bin' failed: 13, "Permission denied". Terminating temporary process.
    The repository never shows any files.
    Any ideas?

    To continue the XCode/Perforce integration discussion a little further.
    Once they have basic XCode/Perforce integration working has anyone been able to get their project file automatically checking out.
    Here is the use case we are having problems with:
    1. Your project including all source, project file and resources is version controlled in Perforce
    2. You can successfully go to edit a file such as main.m and be prompted to "SCM Edit" the file. Choosing to "SCM Edit" sucesfully checks out the file in perforce.
    3. Double clicking on the project file allows you to edit the file BUT you notice it NEVER gets checked out in Perforce. Further when you go to exit XCode it asks if you if you want to "Close and Lose" changes you have made to the project file.
    As everyone is aware the project file needs editing quite often. Not having the IDE check it out on your behalf becomes annoying quite quickly.
    I have watched the SCM actions reported by XCode closely (apple-shift-v) and the commands that are being executed by XCode seem pretty right. My guess is that xcode isn't interpreting the result of the following command correctly:
    p4 opened <base>/projects/myworkspace/main/TestProject.xcodeproj/...
    I notice with interest in the "Source Code Management" section here http://developer.apple.com/releasenotes/DeveloperTools/RN-Xcode/index.html that Apple have recently been doing quite a bit of work with Xcode/Perforce integration.
    Having project files broken in SCM integration seems obvious. Surely I must be missing something?
    Any thoughts/fixes/comments/suggestions or updates very welcome
    Thanks for your time,
    Xumii Dev Team

  • Updating LabVIEW version and Perforce

    I have several large projects in LabVIEW that were previously saved into perforce.  The issue I'm having is that after upgrading to a newer version of LabVIEW (2011) every time I open one of these projects that were saved in a pervious version (2010) I have to go through all the hassle of having everything recompile for the new version, also it can become a headache to tell what I've actually changed and what simply wants to be saved again because of the version change.  So my question is this:  how can I check out an entire project in perforce (and all the VIs within that project), have labview update all the files in that project (essentially I want everything to act as if it were opened, saved, then closed so all labview version changes, type def changes etc. will be saved) and then check it all back into perforce.
    There just has to be an easier way than doing this file by file...
    Thanks in advance.

    Do you have P4V (the visual Perforce client) installed?  If not, install it, it's free.  Then, in P4V, right-click on the folder containing your LabVIEW project and check out the entire folder.  Open the project in LabVIEW, Save All, and then back in P4V submit the recompiled code.

  • TestStand 3.1 and Perforce 2005.1

    I am using TestStand 3.1 with Perforce 2005.1 integrated into Teststand.  When I try closing teststand or saving a workspace it freezes and crashes.  Also, another user created a workspace and when I try and modify or save it it asks for HIS password even though he doesn't have it checked out or anything.  Has anybody used these two together and have any advice?
    Thanks,
    Brian

    Hi Brian,
    There are some issues that have been introduced with the new versions of Perforce and we are working to fix them in future versions.  I am not sure if this is a result of the newer version of Perforce or if there may be something else causing this behavior.  I was hoping that you could give me detailed information of what you are doing step by step as well as what you see happening when you are having the trouble.  The more detail you can give me, the better I can try and reproduce this behavior here.  We are trying to get all the cases that are having conflicts with the newer versions of Perforce so that we can fix these conflicts in future vesions.
    Thanks,
    Caroline Tipton
    Data Management Product Manager
    National Instruments

  • Sorting and Grouping in Projects View

    In Projects view, when either of two of the three grouping options is selected, there are two sorts in effect: the groups themselves are sorted, and the contents of each group are sorted. These sorts are handled differently, depending on the grouping selected and the sort order selected.
    (It appears that there is a bit of the old Apple voodoo in here. The results are arbitrary , but they seem to have been carefully chosen to meet most users expectations. That is to say -- and this is an Apple programming trait -- the arbitrariness is faithful to the expected users' needs, not to logic.)
    There are four sorts available, and three groupings
    Sorts:
    . Name
    . Date -- Oldest First
    . Date -- Newest First
    . Library
    Groupings:
    . Ungrouped
    . Group by year
    . Group by folder
    So that's twelve possible ways to display Projects in Projects view.
    Let's look at a few of them. I'm going to refer to the groups as "Year groups" or "Folder groups" and to the contents of the groups as "Projects". So there is sorting of the groups, and sorting of the contents of the groups (same as "within the group"). These I'll refer to as "Groups sorting" and "Projects sorting".
    Sort: Date -- Newest First
    Grouping: Group by Year
    Result: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
    Sort: Date -- Oldest First
    Grouping: Group by Year
    Results are as expected; a reversal of the "Newest First" sort, but with the same groups: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
    Sort: Name
    Grouping: Group by Year
    Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are sorted alphabetically, descending.
    Sort: Library
    Grouping: Group by year
    Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector. (Note that this last is literal: a Project named "Aardvark Close-ups" if it's in a Folder named "Zoography" will be listed after all the projects in "Yellow Paintings" and all the Projects in "X-rays, thoracic" if those Projects are in alphabetical order by Folder name in the Library. You can see all the Projects in your Library listed on the Library tab of the Inspector by "{Option}+clicking" the disclosure triangle next to "PROJECTS & ALBUMS" twice.)
    Sort: Date - Newest First
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, newest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder.
    Sort: Date - Oldest First
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, oldest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
    Sort: Name
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted alphabetically by name, descending. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
    Sort: Library
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector (see note above). Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are listed in the order they appear in the Library).
    Ernie [asked:|http://discussions.apple.com/thread.jspa?threadID=2816124&tstart=0]
    +I see those icons but note that those projects in folders will be in different sections arranged alpha, and then date within. Am I correct on that?+
    The answer is, it depends.
    If "Group by year" is selected, the Groups-sorting will always be by date, regardless of the sort order specified. The Groups-sorting order will follow whatever is specified for the Projects sort order (or default to "oldest first").
    If "Group by folder" is selected, the Groups-sorting will always be alphabetical, descending, regardless of the sort order specified. (So if you use Projects view, take care in naming your Folders. Use prefixes if needed to force a desired alpha sort.)
    If "Ungrouped" is selected, there are no Groups and perforce no Groups-sorting.
    That's all I have to say on this topic (today).
    Message was edited by: Kirby Krieger

    In Projects view, when either of two of the three grouping options is selected, there are two sorts in effect: the groups themselves are sorted, and the contents of each group are sorted. These sorts are handled differently, depending on the grouping selected and the sort order selected.
    (It appears that there is a bit of the old Apple voodoo in here. The results are arbitrary , but they seem to have been carefully chosen to meet most users expectations. That is to say -- and this is an Apple programming trait -- the arbitrariness is faithful to the expected users' needs, not to logic.)
    There are four sorts available, and three groupings
    Sorts:
    . Name
    . Date -- Oldest First
    . Date -- Newest First
    . Library
    Groupings:
    . Ungrouped
    . Group by year
    . Group by folder
    So that's twelve possible ways to display Projects in Projects view.
    Let's look at a few of them. I'm going to refer to the groups as "Year groups" or "Folder groups" and to the contents of the groups as "Projects". So there is sorting of the groups, and sorting of the contents of the groups (same as "within the group"). These I'll refer to as "Groups sorting" and "Projects sorting".
    Sort: Date -- Newest First
    Grouping: Group by Year
    Result: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
    Sort: Date -- Oldest First
    Grouping: Group by Year
    Results are as expected; a reversal of the "Newest First" sort, but with the same groups: Year groups are sorted in the same order as Projects. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together.
    Sort: Name
    Grouping: Group by Year
    Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are sorted alphabetically, descending.
    Sort: Library
    Grouping: Group by year
    Result: Year groups are sorted by year, oldest first. Projects which span multiple years are put in multi-year groups. Projects with the same spans are grouped together. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector. (Note that this last is literal: a Project named "Aardvark Close-ups" if it's in a Folder named "Zoography" will be listed after all the projects in "Yellow Paintings" and all the Projects in "X-rays, thoracic" if those Projects are in alphabetical order by Folder name in the Library. You can see all the Projects in your Library listed on the Library tab of the Inspector by "{Option}+clicking" the disclosure triangle next to "PROJECTS & ALBUMS" twice.)
    Sort: Date - Newest First
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, newest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder.
    Sort: Date - Oldest First
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted by date, oldest first. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
    Sort: Name
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are sorted alphabetically by name, descending. Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are sorted alpha-name, descending).
    Sort: Library
    Grouping: Group by folder
    Result: Folder groups are sorted alphabetically by name, descending. Projects are listed in the order they occur in the Library structure shown on the Library tab of the Inspector (see note above). Clicking a Folder's name in the Project viewer drills down to show the sub-Folders and Projects in the clicked Folder (where, again, Folder groups are sorted alpha-name, descending, and Projects are listed in the order they appear in the Library).
    Ernie [asked:|http://discussions.apple.com/thread.jspa?threadID=2816124&tstart=0]
    +I see those icons but note that those projects in folders will be in different sections arranged alpha, and then date within. Am I correct on that?+
    The answer is, it depends.
    If "Group by year" is selected, the Groups-sorting will always be by date, regardless of the sort order specified. The Groups-sorting order will follow whatever is specified for the Projects sort order (or default to "oldest first").
    If "Group by folder" is selected, the Groups-sorting will always be alphabetical, descending, regardless of the sort order specified. (So if you use Projects view, take care in naming your Folders. Use prefixes if needed to force a desired alpha sort.)
    If "Ungrouped" is selected, there are no Groups and perforce no Groups-sorting.
    That's all I have to say on this topic (today).
    Message was edited by: Kirby Krieger

  • Partial solution for sql developer 2.1 EA2 and 9i db

    While this bug resolved, I have found a solution to use sql developer 2.1 EA2 and db 9i.
    The solution has been to mix two post:
    1.- Re: 2.1: Packages and compilation icons
    2.- Issue with viewing packages in SQL Developer EA2
    The problem seems to be acces to the tables ALL_PLSQL_OBJECT_SETTINGS and DBA_PLSQL_OBJECT_SETTINGS , deleting the reference in the xml file that it's at the post 1, I can see the Packages, Procedures and Functions of db 9i.

    In SQL Developer 2.1, the CVS and Perforce extensions will be available through the Check for Updates facility. We will update the Check for Updates this week, so that you can use them with SQL Developer EA2.
    Sue

  • Robohelp 8 integration via the Microsoft Source Control API (Perforce/Subversion)

    Robohelp 8 claims to support the Micorsoft Source Control API, which allows third party source control systems to be used with it. Unfortunately, it seems to work great with Subversion (third party plug-in required) and Perforce until we rename a file. Then it fails. For Perforce, it fails with no error. The file just doesn't get renamed. For Subversion, we get an ugly error from the plug-in, but after consulting with the plug-in's developers (PushOK) and given the same problem in Perforce, I think this is an RH8 bug.
    Has anyone else seen this, or does anyone else have experience with this?
    Thanks in advance!
    Jason

    was routing problem

  • LVCompare

    I've got a LabVIEW 7 project that has about 1000 VIs and controls, call it Lab Original.  I made a modification that involved changing about 100 VIs, adding some, removing some -- call it Lab New.  I now want to make a third version that combines some features of Original and New, but am not 100% certain which VIs have been changed, and which are essentially the same.  Everything is under Version Control (Tortoise SVN), so at least the files are easily kept organized.  However, I can't easily use Date/Time information to distinguish changed and identical files, nor can I use ordinary comparison tools as simply opening a file can often lead to a (trivial) binary change.
    Fortunately, there's LVCompare.exe, which has the ability to compare two VIs, looking at differences in the Block Diagram without caring about the appearance, size, or position of the various objects.  This utility acts like a DOS command -- you call it from the Command Line and pass it parameters and switches -- it does the compare and gives you a three-window display of the two VIs and their differences (if any), similar to what you see if you use the LabVIEW Compare Tool.  But there are some caveats.
    First, the two file arguments must be distinct.  There's a note that says if they are in different LabVIEW Projects, then the Project environments will be different, but I haven't figured out what this means nor how to use it (even with VIs that are truly in a LabVIEW Project).  I've "programmed around" this problem by changing the extension of one of the VIs to .tmpvi, calling LVCompare, and then renaming it back to .vi when I'm done.
    I've "wrapped" the calls to LVCompare in a set of VIs that let me deal with the two folders holding the Lab Original and Lab New files (and folders).  I first split the set of files into "Files unique to Lab Original", "Files unique to Lab New", and "Files in both places".  Clearly I only need to run LVCompare on the latter.  I build the arguments needed for LVCompare, pass the files in, then wait for LVCompare to show me the differences.
    The only remaining problem is that LVCompare doesn't "return" anything -- in particular, the only way to tell if two files are different is to actually look at the output of LVCompare!  What I'd really like to have is some form of output that can signal if the files are different or the same so that I can let the program crank through all of my files without having to use my own eyes as the indicator of a difference.
    My initial trial of this system is certainly promising -- even though LVCompare can be a bit slow (a few seconds for each file), it (a) seems to work even on LabVIEW 7.0 files, (b) leaves the files that it is comparing intact, and (c) if there are files "missing" when it tries to open a VI, it simply plows ahead and does the comparison anyway after "giving up" on finding the files.
    I have some ideas about how to trick LVCompare into telling me if there are differences or not.  If anyone has suggestions, they'd be most welcome.
    Bob Schor

    Hi, Bob,
    Long time ago it was also necessary for me. Somewhere I have found one "undocumented" method, so it was possible to compare VIs "programmatically".
    May be it helps for you as well. Disclaimer - use it at your own risk.
    Andrey.
    Attachments:
    Differences Programmatically.vi ‏22 KB

  • RoboHelp 8 Integration with Perforce

    I would like to integrate RoboHelp 8 with Perforce to allow our writing team to work on different topics within the same help project at the same time. However, I am having a difficult time locating a document that definitively describes the set up and configuration process. Can someone on this forum provide their instructions for integrating RoboHelp and Perforce?
    Thank you in advance for your assistance.

    Can you please tell us the type of output you are generating? Is it a CHM file? Also there are a number of variables in your problem that we need to ask about in order to get to the bottom of things.
    You say you can't see the problem. Do you mean that when you view the output all the topic titles and TOC pages display the French correctly? If so, who is getting the problem?

  • Perforce Integratio​n 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/B371AC6D6CC​E335E86256CE2004A5853?OpenDocument

  • 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

  • Looking for Source Control suggestions

    I'm a non-professional "at home" programmer and want to set up and experiment with Source Control. The available options seem to be CVS, Subversion and Perforce, although I gather that CVS is 'old technology' replaced by Subversion.
    My requirements (desires)
    A) Run on 10.4.11
    B) integrate with XCode, but can be accessed without it when desired
    C) have a GUI interface (can use command line, but prefer GUI)
    D) can store non-text documents (like Word Processing and Spreadsheets - not necessarily graphics)
    What are advantages/disadvantages of Subversion vs Perforce?
    What are the best GUIs for Subversion?
    Any suggestions / advice would be appreciated.
    Thanks for any help.

    frankinmelrose wrote:
    The available options seem to be CVS, Subversion and Perforce, although I gather that CVS is 'old technology' replaced by Subversion.
    There are actually quite a few more than that. Plus, Perforce is commercial software. I believe it can be used for free under some circumstances, such as yours.
    It sounds like you have bought into the Subversion propaganda There is nothing wrong with CVS. It is super easy to setup and use. It is more a competitor to Subversion than being replaced by it. In fact, I would now call Subversion 'old technology' replaced by Git.
    My requirements (desires)
    A) Run on 10.4.11
    They all do.
    B) integrate with XCode, but can be accessed without it when desired
    Most do.
    C) have a GUI interface (can use command line, but prefer GUI)
    Most do. There may be 3rd parties that have build GUIs in some cases.
    D) can store non-text documents (like Word Processing and Spreadsheets - not necessarily graphics)
    They all do.
    I can't answer any other questions as I've never really used Subversion or Perforce. I tried to install the Subversion server but gave up because it was way too complicated. I like CVS - sweet and simple.

Maybe you are looking for