Chris Seawood wrote:
> I think the only truly XP way to do it would be to follow NSPR's example
> and rename the library with each major revision.
I recommend that you go for the platform native way and not use NSPR's
XP way. Although it achieves the same goals as the platform native way,
people consider NSPR's XP way nonstandard, which leads to many questions
and bug reports.
> I'd prefer to use
> unix's soname feature which will allow us to distinguish between minor
> releases of the same major release branch of a library but I don't know
> if that feature exists for win32 or classic mac.
There are two issues here -- version numbers in file names and internal
versioning info (which won't be lost if you rename the files).
Win32 DLLs usually put the version numbers in the file names. So NSPR's
nspr4.dll is in fact not an unusual name for Win32.
Win32 also has a VERSIONINFO resource that you can link into your
DLLs. (Sort of the equivalent of Unix's SONAME but more comprehensive.)
This allows you to specify all kinds of version information about your
library. NSPR and NSS DLLs have VERSIONINFO resource.
I don't know about classic MacOS.
Wan-Teh
