(Reporter) How does one use OpenGL PLI on Linux? (SOC) (OpenGL PLI) (nc-OpenGL) (Linux)

Abstract
Previously, we discussed the issue in the Windows nc-greenpli line. If you want to perform PLI in Linux nc-greenpli, some places are not exactly the same ‧

Introduction
The differences between Windows and Linux nc-OpenGL are as follows: First, Windows uses Visual C ++ 6.0 kernel, and Linux uses GCC kernel. Second: windows and Linux have the same design path. Fortunately, if you use the standard C statement to modify PLI, you can skip windows porting to Linux ‧

Compiler: Visual C ++ compiler is compiled *. DLL, GCC compiled *. so, fortunately, Cadence provides PLI wizard with the same GUI in Windows and Linux, so that we only need to set the next step, you can call visual c ++ or GCC manually *. DLL or *. so ‧

Set the path for Windows as long *. dll can be automatically captured in the current path, or in c: \ Program Files \ Cadence design systems \ ius \ tools \ bin \, NC-OpenGL; however, this is not true for Linux. You must specify the number of changes in the environment. If you want *. so must be set as follows:

Setenv LD_LIBRARY_PATH.: $ LD_LIBRARY_PATH

The tool of cadence will depend on the variable LD_LIBRARY_PATH. this parameter indicates the current project, and $ LD_LIBRARY_PATH indicates the setting of the original LD_LIBRARY_PATH. In this way, NC-OpenGL is used by the attacker to capture his own *. so ‧