Changes between Version 7 and Version 8 of AppLibraries

Timestamp:

Dec 8, 2011, 1:10:52 PM (13 years ago)

Author:

davea

Comment:

--

AppLibraries

@@ -1 +1 @@
 = Dynamic library naming issues =
 
-Suppose your application uses a dynamic library, say '''vcomp90.dll'''.
+Suppose your application uses a dynamic library, say '''example.dll'''.
 Recall that [BoincFiles BOINC files are immutable].
-Hence there is a problem if either
+If you use the physical name '''example.dll'''
+there will be a problem if either
 
  * You support multiple platforms (say, Win32 and Win64),
-   and there are different versions of '''vcomp90.dll''' for each platform.
+   and there are different versions of '''example.dll''' for each platform.
  * You need to update to new versions of the library.
 
-One solution is to give the libraries names that encode the
-platform and version number,
-e.g. '''vcomp90_win32_1_17.dll''' and '''vcomp90_win64_1_17.dll'''.
-However, this may be infeasible
-because the name '''vcomp90.dll''' is embedded in your Makefiles and
-would be difficult to change.
-
-A second solution, which doesn't require changing Makefiles,
-is to give the libraries different physical names but the same logical name.
-To do this, use something like the following in your
-[AppVersionNew#Theversiondescriptionfile version description file]:
+The easiest solution is:
+ * Give the libraries physical names that encode the platform and version number,
+   e.g. '''example_win32_1_17.dll''' and '''example_win64_1_17.dll'''.
+ * Use '''example.dll''' as the logical name.
+  To do this, use something like the following in your
+  [AppVersionNew#Theversiondescriptionfile version description file]:
 {{{
 ...
   <file>
-    <physical_name>vcomp90_win32_1_17.dll</physical_name>
-    <logical_name>vcomp90.dll</logical_name>
+    <physical_name>example_win32_1_17.dll</physical_name>
+    <logical_name>example.dll</logical_name>
     <copy_file/>
 ...
@@ -31 +27 @@
 The '''copy_file''' flag tells the BOINC to copy the library to
 the application's runtime directory.
+
+== Avoiding name conflicts ==
+
+The search order for libraries is:
+
+ 1. The project directory
+ 1. The slot directory
+ 1. other directories
+
+Hence if you use '''example.dll''' as a physical name in one app version,
+other app versions will use that library even if they
+use the above scheme.
+
+To avoid this problem, use logical names that don't conflict with physical names.