You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: Cpp-C/Eta/README.md
+30-30
Original file line number
Diff line number
Diff line change
@@ -139,39 +139,39 @@ Shared library use is similar to static library use, however there are several k
139
139
140
140
Library Name Package Version
141
141
------------ ---------------
142
-
librssl.lib* eta3.5.0.L1
143
-
librsslVA.lib eta3.5.0.L1
144
-
librsslVACache.lib eta3.5.0.L1
145
-
libansi.lib eta3.5.0.L1
146
-
libdacs.lib eta3.5.0.L1
142
+
librssl.lib* eta3.5.0.G1
143
+
librsslVA.lib eta3.5.0.G1
144
+
librsslVACache.lib eta3.5.0.G1
145
+
libansi.lib eta3.5.0.G1
146
+
libdacs.lib eta3.5.0.G1
147
147
148
148
*librssl.lib includes JsonConverter
149
149
150
150
##### Shared Library Manifest
151
151
152
152
Library Name Package Version
153
153
------------- ---------------
154
-
librssl.dll eta3.5.0.L1
155
-
librssl.lib eta3.5.0.L1
156
-
librssl.pdb eta3.5.0.L1
157
-
librsslVA.dll eta3.5.0.L1
158
-
librsslVA.lib eta3.5.0.L1
159
-
librsslVA.pdb eta3.5.0.L1
160
-
librsslVACache.dll eta3.5.0.L1
161
-
librsslVACache.lib eta3.5.0.L1
162
-
librsslVACache.pdb eta3.5.0.L1
163
-
librsslJsonConverter.dll eta3.5.0.L1
164
-
librsslJsonConverter.lib eta3.5.0.L1
165
-
librsslJsonConverter.pdb eta3.5.0.L1
154
+
librssl.dll eta3.5.0.G1
155
+
librssl.lib eta3.5.0.G1
156
+
librssl.pdb eta3.5.0.G1
157
+
librsslVA.dll eta3.5.0.G1
158
+
librsslVA.lib eta3.5.0.G1
159
+
librsslVA.pdb eta3.5.0.G1
160
+
librsslVACache.dll eta3.5.0.G1
161
+
librsslVACache.lib eta3.5.0.G1
162
+
librsslVACache.pdb eta3.5.0.G1
163
+
librsslJsonConverter.dll eta3.5.0.G1
164
+
librsslJsonConverter.lib eta3.5.0.G1
165
+
librsslJsonConverter.pdb eta3.5.0.G1
166
166
167
167
#### Linux
168
168
Shared library use is similar to static library use, however there are several key differences. The shared library can be stored in a different location on the machine than the application using it. Ensure that the shared library location is present in the LD_LIBRARY_PATH being used by the application. The library use can be confirmed by using the ldd command on the application. This will show the shared library dependencies and where they are being resolved to.
169
169
170
170
In addition, several versions of a shared library can co-exist on the machine. This allows for easy upgrade of functionality by deploying a newer shared library. It is important to ensure that the application is using a version that is binary compatible to the library that it originally linked with.
171
171
172
-
To help with this, Transport API provides several versioning mechanisms for its open source and closed source shared libraries. Each open source library is provided with its package version appended to the end. For example, librssl.so.3.5.0.L1. For closed source shared libraries, the binary version is appended to the name. For example, librsslVACache.so.3. Embedded in each library is a shared object name (soname) that conveys binary compatibility information. For example, assuming that the embedded soname is librssl.so.1, if binary compatibility were to change in UPA, this embedded soname would be updated to be librssl.so.2. This naming convention is intended to help protect applications from using a non-compatible version of the shared library.
172
+
To help with this, Transport API provides several versioning mechanisms for its open source and closed source shared libraries. Each open source library is provided with its package version appended to the end. For example, librssl.so.3.5.0.G1. For closed source shared libraries, the binary version is appended to the name. For example, librsslVACache.so.3. Embedded in each library is a shared object name (soname) that conveys binary compatibility information. For example, assuming that the embedded soname is librssl.so.1, if binary compatibility were to change in UPA, this embedded soname would be updated to be librssl.so.2. This naming convention is intended to help protect applications from using a non-compatible version of the shared library.
173
173
174
-
The Transport API provides a helpful script that will create soft links for the appropriate library names, allowing for applications to link against a consistent name, but still leverage product and binary compatibility versioning. For example, librssl.so.3.5.0.L1 is the file; librssl.so.1 and librssl.so are symlinks to librssl.so.3.5.0.L1. Similarly for closed source example, librsslVACache.so.1 is the file; librsslVACache.so.3.5.0.L1 and librsslVACache.so are symlinks to librsslVACache.so.1. The following script located at the base level of the package, creates the appropriate symlinks, and can be run as follows:
174
+
The Transport API provides a helpful script that will create soft links for the appropriate library names, allowing for applications to link against a consistent name, but still leverage product and binary compatibility versioning. For example, librssl.so.3.5.0.G1 is the file; librssl.so.1 and librssl.so are symlinks to librssl.so.3.5.0.G1. Similarly for closed source example, librsslVACache.so.1 is the file; librsslVACache.so.3.5.0.G1 and librsslVACache.so are symlinks to librsslVACache.so.1. The following script located at the base level of the package, creates the appropriate symlinks, and can be run as follows:
175
175
176
176
./LinuxSoLink
177
177
@@ -180,22 +180,22 @@ The Transport API provides a helpful script that will create soft links for the
0 commit comments