Menu
▾
▴
freemint-discuss
|
From: Thorsten O. <ad...@th...> - 2018-08-05 02:06:52
|
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. 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. And then: should the default libs (for plain 68000) be installed in the base directory, or also in a dedicated sub-directory, like the others? That would make it easier to switch configurations by just setting SLBPATH accordingly, without having to copy around actual files. |
|
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. |
|
From: Miro K. <mir...@gm...> - 2018-08-05 11:53:07
|
Yes, those are very good questions. I would say /mint/slb (and its MagiC counter part /gemsys/magic/xtension) and /gemsys/ldg are indeed a de facto standard but it doesn't answer your concern about different CPU builds. On the other hand, there really isn't any real world scenario (as of yet) requiring the user to care about it -- applications like "setup.app" from various software packages (aniplayer comes to my mind) simply copy all *.slb into given directory. Different CPU builds are solved via setup.app - you can choose your favourite CPU build but only one. So if the user knows that all his SLBs are in some directory, he would just copy new SLB there, either automatically (setup.app) or manually. To make this totally right I'd say FreeMiNT would need to look after $SLBPATH/$CPU in addition to just $SLBPATH, very similar what mintloader.prg does for freemint modules ($SYSDIR + $SYSDIR/<machine specific folder>). And in that case we can come up with any naming scheme we like - m68000, m6802060, m5475, ... but it doesn't look like a priority to me. On Sun, 5 Aug 2018 at 04:07, Thorsten Otto <ad...@th...> wrote: > 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. > > 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. > > And then: should the default libs (for plain 68000) be installed in the > base > directory, or also in a dedicated sub-directory, like the others? That > would > make it easier to switch configurations by just setting SLBPATH > accordingly, > without having to copy around actual files. > > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freemint-discuss mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemint-discuss > -- MiKRO / Mystic Bytes http://mikro.atari.org |
|
From: Thorsten O. <ad...@th...> - 2018-08-05 14:51:31
|
On Sonntag, 5. August 2018 13:52:47 CEST Miro Kropáček wrote: > applications like "setup.app" from various software packages (aniplayer > comes to my mind) simply copy all *.slb into given directory. Yes, but having a to write a "setup.app" would be extra effort. Also i'm currently speaking about more standard libraries like zlib and pnglib that are not specific to a single application (i just wonder that apparently nobody has built such things yet). >To make this totally right I'd say FreeMiNT would need to look after >$SLBPATH/$CPU in addition to just $SLBPATH, very similar what mintloader.prg >does for freemint modules ($SYSDIR + $SYSDIR/<machine specific folder>). That would make sense. But of course that currently does not help much currently as long as this is not implemented. |
|
From: Paul W. <pau...@gm...> - 2018-08-07 04:55:59
|
All the ARAnyM setups I have used are usually with MiNT and (loosely) based around the (now old) AFROS CD fs structure. Of all the setups I have used, only one had SLB placed anywhere but C:/mint/slb, and that was the French created OpenGL enable ARAnyM + MiNT. I believe that was more to do with the fact that they also develop with LDG, so theres were in C:/gemsys/slb next to C:/gemsys/ldg. As far as I understand it, MagiC's use of C:/gemsys/magix/extension is more to do with the fact that the above where not in use yet (LDG and MiNT + SLB), so there really was not a need for them to be anywhere else. Although I would like to use MagiC with my drive setups, it not going to happen in the foreseeable future. But I do use them in various combinations, and what I found was that certain versions of SLB wont run on certain setups. So I maintain a C:/mint/slb with 68020-060 and C:/gemsys/slb for anything else, incl. 68000 (which is usually the only other ones needed), next to C:/gemsys/ldg Mikro is right tho, apart from ARAnyM & other Emu setups, on real HW there is not even a need for what I've maintained, unless you are sharing a CF card across different architectures, even then C: boot and auto needs to be different anyway. I believe some magic extensions cant be loaded if they are not in the mention folder, hardcoded in a loader somewhere, but I dont remember what. If you use MiNT, and require some (old) TOS apps to work, SLB's need to be on C:, so C:/mint/slb covers both. If you share the fs with 68000 (or not MiNT), then C:/gemsys/slb is safe for them, and it should work with Musashi loaded 68000 on CF/FireBee as well. If you only use specific hardware, but swap between MiNT and TOS boots, I would still place the HW specific versions in C:/gemsys/slb, and 68020-060 in C:/mint/slb, at least you can easily share them with others, knowing what architecture they are. My 2cents worth Paul On Mon, Aug 6, 2018 at 2:51 AM, Thorsten Otto <ad...@th...> wrote: > On Sonntag, 5. August 2018 13:52:47 CEST Miro Kropáček wrote: > > applications like "setup.app" from various software packages (aniplayer > > comes to my mind) simply copy all *.slb into given directory. > > Yes, but having a to write a "setup.app" would be extra effort. Also i'm > currently speaking about more standard libraries like zlib and pnglib that > are > not specific to a single application (i just wonder that apparently nobody > has > built such things yet). > > >To make this totally right I'd say FreeMiNT would need to look after > >$SLBPATH/$CPU in addition to just $SLBPATH, very similar what > mintloader.prg > >does for freemint modules ($SYSDIR + $SYSDIR/<machine specific folder>). > > That would make sense. But of course that currently does not help much > currently as long as this is not implemented. > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freemint-discuss mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemint-discuss > |
Thanks for helping keep SourceForge clean.
X