Date: Tue, 6 Jan 2004 00:07:06 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 255 ************************************************** Monday 05 January 2004 Number 255 ************************************************** Subjects for today 1 Re: Any new UX2BS testers? : Andreas Buening **= Email 1 ==========================** Date: Mon, 05 Jan 2004 13:33:06 +0100 From: Andreas Buening Subject: Re: Any new UX2BS testers? knut st. osmundsen wrote: [snip] > As for libtool porting, I of course make sure the dll name is no more > than 8 chars long (incuding any release number stuff). The first two > numbers in the release string (if present) is appended with no dots and > not in decimal but 36 digit numbers, 0-9A-Z, to save precious space. > (Any sugestions about ways to encode a couple of numbers in a more > condense way is welcome.) I don't like this because - this leads to unreadable DLL names (foo3243a.dll) - if you have programs linked with different versions of libfoo, you have to have many foo*.dll on your system, even if those versions are binary compatible - it doesn't help if the library name is 8 bytes or longer - if the library name is 6 or 7 byte, I doubt, you can compress a version string like 1.24.5 into 1 or 2 bytes (in a unique and automagically working way) Therefore, IMHO the best solution would be - to use the library name as is, without any release numbers - to strip (only) the dll name down to 8 characters if necessary - and, if the 8 char dll name isn't unique (e.g. libverylongnamebar and libverylongnamefoo would both lead to verylong.dll) or if a new library version isn't binary compatible with the old version, provide a way to specify the final dll name by hand: e.g. an env. var. EMX_LIBTOOL_DLLNAME which overrides the default (verylong.dll). Then you wouldn't get a new dll name for every tiny bugfix release. > The porting is going slowly (but I've got both DLLs and libs now) since > I encountered some trouble telling libtool about import libraries. One > would think the Win32 guys had tought libtool that concept years ago, > but not. libtool 1.4.x has the concept of import libraries from Win32 (somewhere). They're created in the .intl subdirectories. [snip] > - shared mode (default): > 1. libfoo_dll.a > 2. foo_dll.a > 3. libfoo.a > 4. foo.a > 5. foo.dll > 6. libfoo_s.a > 7. foo_s.a [,..] Isn't it slightly too complicated? :-) Bye, Andreas _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs