From: news@cct-net.co.uk   
      
   On 17/08/2025 18:52, Arne Vajhøj wrote:   
   > On 8/17/2025 11:24 AM, hb0815 wrote:   
   >> On 8/15/25 02:33, Arne Vajhøj wrote:   
   >>> On 8/12/2025 11:09 PM, Lawrence D'Oliveiro wrote:   
   >>>> On Tue, 12 Aug 2025 19:08:51 -0400, Arne Vajhøj wrote:   
   >>>>> mysql055_root:[lib.alpha]libclientlib/lib   
   >>>>> mysql055_root:[lib.alpha]libsql/lib   
   >>>>> mysql055_root:[lib.alpha]libmysys/lib   
   >>>>> mysql055_root:[lib.alpha]libdbug/lib   
   >>>>> mysql055_root:[lib.alpha]libstrings/lib   
   >>>>> mysql055_root:[lib.alpha]libvio/lib   
   >>>>> mysql055_root:[lib.alpha]libz/lib   
   >>>>> mysql055_root:[lib.alpha]ssl_libssl32/lib   
   >>>>> mysql055_root:[lib.alpha]ssl_libcrypto32/lib   
   >>>>   
   >>>> Is there some equivalent to “-L«dir»” to add a common directory to a   
   >>>> linker search path so you can just shorten most of that to something   
   >>>> more like “-lclientlib -lsql -lmysys -ldbug -lstrings -lvio -lz”?   
   >>>   
   >> ...   
   >>> You can omit location on all libraries except the first and   
   >>> let the sticky default mechanism add it.   
   >>>   
   >>> (I don't think that is a nice solution)   
   >   
   >> You may not like it, but using the file specification stickiness or   
   >> RMS related name context processing is the only useful method to avoid   
   >> repeating the directory specification. This works on the command line   
   >> as well as in option files. And you can have more than one library on   
   >> a single option line, anyway.   
   >   
   > It can be used.   
   >   
   > But if someone edit the list and either remove libraries or   
   > add libraries, then it is pretty easy to mess up.   
   >   
   >> If you have GNV, you can use its linker wrapper. However, it requires   
   >> naming the object libraries in Unix style. Although a "libfoo.olb"   
   >> works, there is no way to use an "foo.olb" (and you can't easily get a   
   >> full map with cross references). So this will not work for ssl_* in   
   >> the shown link command. Yeah, you can create (symbolic) links ...   
   >   
   > I did not even consider GNV.   
   >   
   >>> You can setup default libraries with LNK$LIBRARY* logicals.   
   >>   
   >> In your example you would need 9 logicals: LNK$LIBRARY,   
   >> LNK$LIBRARY_1, ..., LNK$LIBRARY_8. There is no _0 and  they must all   
   >> be defined. The suffixes must start with 1 and must not have a gap in   
   >> numbering. You can't use a search list. Additionally, the link command   
   >> line doesn't show that non-system object libraries are used at all.   
   >   
   > It is an option that I considered relevant for the question on   
   > how to shorten link commands.   
   >   
   > I would not use it in this case.   
   >   
   > As an old Fortran programmer then I find it quite natural that   
   > it starts with _1 and not _0.   
   >   
   > :-)   
   >   
   >>> You can create shareable images and stuff all of them into   
   >>> a shareable library.   
   >>   
   >> Then the resulting image or application is no longer "statically"   
   >> linked: you need the shareable image at runtime. You have to create a   
   >> shareable with as many universal symbols, aka symbol vector entries,   
   >> as global symbols in the libraries - just to avoid specifying a couple   
   >> of file paths in the link command.   
   >   
   > There is no free lunch.   
   >   
   > It is an option for the question on how to shorten link commands.   
   >   
   > I would not use it in this case either.   
   >   
   > I don't even think I have ever created such a shareable library. But   
   > everyone is using one (IMAGELIB).   
   >   
   > Arne   
      
   Can you not use make, MMK (or equiv) utility?   
      
   --   
   Chris   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)