How to run applications developed by Vega on other machines

Many of my friends have asked this question. I remember what I answered before. I 'd like to summarize it and share it with you.

There are three methods:
1. Of course, Vega is installed on other machines.
2. Package the dynamic library and lelicence by yourself. Note that you can store the dynamic library as long as yourProgramYou can find it (a programming book teaches you how to find a dynamic library). You must place the licence file in the same folder location as your own machine.

3. Actually, method 3 is the correct method.
Vega has a development version and a running version. We usually use a development version, which is up to 3.7.1, the running version is used to run applications developed by Vega on other machines. The running version is actually the basic dynamic library + licence of Vega, the running version has a relationship with the Development version. When you buy a running version from an American manufacturer, you must provide the user information about the Development version you bought. Of course, the running version is much cheaper, the running version is up to 3.6,

Compile your Vega program statically on the machine of the development version. (The running version does not provide DLL for special effects,, and other modules. Therefore, you must perform static compilation ), in Project-> Settings-> C ++-> General-> Preprocessor definitions, add _ psi_static_libs, ignore_md_warning; choose project-> Settings-> C ++-> code generation-> use run time library and select debug multithreaded. After re-compilation, conflicting error messages will appear, because Vega is written from SGI and transplanted to Windows in C, it conflicts with some libraries in VC ++, generally, the library you want to ignore is added to the ignore libraries in project-> Settings-> link-> category-> input, which is usually the ones in the compilation error prompt, such as mscrvt. dll library In the end, there will be no errors, but there will be warning information, there is no way, American companies no longer provide the new version of Vega. Finally, put the xvsdll. dll in the root directory of your Vega installation in the development version together with your application, so that your application can run on the machine where the development version is installed,
By the way, you have to manually add environment variables after the running version is installed. Otherwise, your program will prompt that you cannot find the library of Vega, how can American companies not make it more humane.

Among the three methods, the third type is recommended. Some people may feel uncomfortable buying a running version. The second type can be used for personal learning. (actually, it is similar to re-installing Vega, lynx is a text file that can be opened in the writing version ). If you provide the licence of your development version, you cannot guarantee its validity. What you get on the internet for decryption is usually through 2015, which is temporary, you can't get a permanent license bound to a machine. Of course, if you can get a permanent license, you should also have a running version.