The library names of the Unix (Linux and Mac) versions of ooRexx added links to
support earlier
ooRexx versions in the form
* Linux
o "lib" name ".so.${ORX_MAJOR}", e.g.
+ librexx.so -> librexx.so.3
librexx.so -> librexx.so.4
....
+ librexxapi.so -> librexxapi.so.3
librexxapi.so -> librexxapi.so.4
...
* MacOS
o "lib" name ".${ORX_MAJOR}.dylib", e.g.
+ librexx.dylib -> librexx.3.dylib
librexx.dylib -> librexx.4.dylib
...
+ librexxapi.dylib -> librexxapi.3.dylib
librexxapi.dylib -> librexxapi.4.dylib
...
The version number in the current ooRexx 5.0 beta on Unix (Linux, MacOS) use in
addition to
${ORX_MAJOR} the subnumbers ${ORX_MINOR}.${ORX_MOD_LVL, thereby unnecessarily
breaking the naming
system, e.g.:
* Linux
o "lib" name ".so.${ORX_MAJOR}", e.g.
+ librexx.so -> librexx.so.3
librexx.so -> librexx.so.4
librexx.so -> librexx.so.5.0.0
....
+ librexxapi.so -> librexxapi.so.3
librexxapi.so -> librexxapi.so.4
librexxapi.so -> librexxapi.so.5.0.0
...
* MacOS
o "lib" name ".${ORX_MAJOR}.dylib", e.g.
+ librexx.dylib -> librexx.3.dylib
librexx.dylib -> librexx.4.dylib
librexx.dylib -> librexx.5.0.0.dylib
...
+ librexxapi.dylib -> librexxapi.3.dylib
librexxapi.dylib -> librexxapi.4.dylib
librexxapi.dylib -> librexxapi.5.0.0.dylib
...
Suggesting to changing the versioned library names of ooRexx 5 to match the
established convention
(using only ${ORX_MAJOR}).
Are there any objections to such a change?
---
If not, where does "CMAKE_SHARED_LIBRARY_PREFIX" get set (which gets used for
setting
"ORX_SHARED_LIBRARY_EXT")?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
