Best way to manager open G code

[jyang72211]

If open G code is downloaded, it would resides in the vi.lib folder.  When the code is used in a program, and the program is checked into source safe (only the program, not the vi.lib), others user will have a lot of broken links, since they do not have the same open G code in their vi.lib. 

What is the best way to save all the open G code used in a separate folder and check that separate folder into source safe?  Also, the main program will be calling the open G code in the separate folder but not in vi.lib.  Nobody likes to relink vi.  Thanks!

[Dennis_Knutson]

All of my OpenG is installed in user.lib and not VI.lib and I have no problems putting user.lib into source code control? Why do you want to change the default installation location or not add the default folder into source code control?

[jyang72211]

Sorry, I meant user.lib.  I don't want to check my user.lib in for the following reasons:

1. I have to copy and paste the user.lib into another location for source safe purposes. If I have my user.lib at muliple locations, I could have a lot of broken links down the road.

2. I only want to check in what is used in user.lib for my program.  i don't want everything in my user.lib to be in source safe. 

[Dennis_Knutson]

I can't help, then. You do not HAVE to paste user.lib into another location to use it with source code control, you don't HAVE to place everything in user.lib into source code control, and you don't HAVE to have user.lib in multiple locations from the perspective of source code control. If you have decided to do this for some reason, then I suggest you contact JKI for an alternative way to install OpenG.

[jyang72211]

Thanks!

[jyang72211]

I am asking this because recently I got some code, where all the open g code are part of the hierarchy.

[crossrulz]

My plan (yet to be implemented) is to put the *.vip files in source control and then rely on people to install the packages with VIPM.  There are also the *.vipc files so you can save which packages are installed.  The *.vipc files can also contain the package files.  So you could create a *.vipc file for each project and then put the *.vipc file on source control.

[Mark_Ramsdale]

Am I missing something here?  I think that you could require the target to have the G files, and then the installation would point to the files, under the premise that they are installed in the user directory.

I like the idea of providing the VIP files, but if this is the case it seems easy enough to have the target install them independently of the source code install, although it is convenient to have them provided for you.

Just 2 cents 🙂