|
From: David G. <dga...@gm...> - 2018-08-05 10:27:40
|
2018-08-05 4:06 GMT+02:00 Thorsten Otto <ad...@th...>: > Not that these are currently used much in FreeMinT (i think the recently added > gemma.slb is the only one), but is there some standard/convention where to > install shared libraries (the actual code that is loaded by Slbopen(), not any > helper libraries you might need in your application). > > The automatic build process currently does not install them i think (only the > development parts). And in the Makefile of eg. gemma, when you do a "make > install", it will be installed to /mint/slb, and cpu-specific subdirectories. > > The question is: is that base-directory more or less standard? I've also seen > pathes like /gemsys/slb, and in MagiC they are usually in installed in / > gemsys/magic/xtension. > I have them myself in /gemsys/slb, also I have placed ldg share libraries inside /gemsys/ldg too. But I don't remember why I put them there and if this is the standard. I thought that was from the times I had a dual system MiNT/MagiC but from your comment above that MagiC expects them in gemsys/magic/xtension I'm not sure anymore. I guess that for MiNT only systems it makes sense to placed them inside /mint/slb but I don't have a strong opinion about it. > Also the names of the cpu-specific sub-directories are questionable. Currently > the same names as the multi-lib directories from gcc are used (m68020-60, > m5475 etc.). Since /mint (or /gemsys) are usually on the boot partition, and > thus on a FAT filesystem, at least m68020-60 is not the best choice. > We should to take care about these things, there are also some network drivers which doesn't fit with the 8+3 limit for FAT boot partition. |