Menu
▾
▴
Re: [KOS] Ports tree
|
From: Lawrence S. <ljs...@us...> - 2015-05-17 00:39:24
|
Well, I’ll take the silence on the list to mean that everyone’s tested it and nobody’s found any problems that haven’t already been fixed. ;-) I replaced the old kos-ports repo with the new one this evening (so now it’s mirrored on sourceforge as well as on github, but the sourceforge one should be considered the canonical repo as of now). I pushed the updates to the ghettoplay-vorbis and hello-ogg examples so that they’ll work with the new vorbis library in the kos-ports tree. The Lua example still needs to be updated. Hopefully I’ll find the time to do that in the next few days or so. The old kos-ports repo is still available, but at a different URL now (replace kos-ports with kos-ports-old). I don’t intend to update the old repo any further, so keep that in mind if you use it for some reason. - Lawrence > On May 4, 2015, at 11:50 AM, Lawrence Sebald <ljs...@us...> wrote: > > At least the ghettoplay-vorbis example does use liboggvorbisplay, as does the hello-ogg example (at least optionally). But, that’s beside the point, since I went ahead and updated it anyway (and split it into three separate ports in the process — libogg, libvorbis, and liboggvorbisplay). ;-) > > > And with that, I’ve pushed out the first version of the new ports tree to a github repository, which can be found here: https://github.com/ljsebald/kos-ports <https://github.com/ljsebald/kos-ports> . I’d appreciate it if others could try it out and make sure it works on other systems than my own. You’ll need to have the KOS_PORTS environment variable pointing to the root of wherever you put the kos-ports tree in order to use it, by the way (and that should be all the setup you’ll need). This was added to the normal kos environ script the other day, by the way. > > In doing this, I’ve updated a few of the ports to use the current upstream versions of their code. Specifically, zlib, libpng, libjpeg, libogg, libvorbis, SDL, Lua, and libtremor have all been updated. Testing those specifically would probably be a good idea (especially SDL, since I haven’t checked that one at all). > > A few example programs will need a few updates. The ones that use liboggvorbisplay will need to be updated to link against all three of libogg, libvorbis, and liboggvorbisplay, for instance. The Lua example doesn’t compile at all now due to API differences between Lua 5.0.0 and 5.3.0. > > - Lawrence > >> On May 2, 2015, at 2:14 AM, Quzar <qu...@ya... <mailto:qu...@ya...>> wrote: >> >> I don't recall seeing anything use liboggvorbisplay before (and I certainly haven't). >> >> Glad to hear this is finally moving forward. >> >> -Donald Haase >> -------------------------------------------- >> On Fri, 5/1/15, Lawrence Sebald <ljs...@us... <mailto:ljs...@us...>> wrote: >> >> Subject: [KOS] Ports tree >> To: cad...@li... <mailto:cad...@li...> >> Date: Friday, May 1, 2015, 10:15 PM >> >> *cough* *cough* Is this thing on? Now >> that I have your attention… >> >> As some of you might know (if you’ve looked at the roadmap >> page on the website), I’ve had this idea of having some >> sort of package manager for the kos-ports tree for a long >> while. Well, I’m happy to say that I’ve finally started >> working on just such a thing. >> >> Now, I’m not going for a package manager in the >> traditional sense of apt or yum on Linux, but rather >> something much more akin to the FreeBSD ports collection. >> The goal of this is to make it exceptionally easy to >> “port” new libraries to the system and have them fit >> right in to the existing collection. Another goal here is to >> defer to the upstream packages wherever possible, rather >> than maintaining old crusty versions of the ports’ code in >> our git repositories (of course, many of the things in >> kos-ports don’t have an upstream as they were made >> directly for KOS, but that’s beside the point). >> >> At the moment, it’s nowhere near perfect (it can’t >> handle package dependencies at the moment, and there are a >> few hiccups with some of the ports as they stand), but I did >> want to put it out there that I’m working on it (not that >> I think anyone else was doing such a thing). >> >> With that out of the way, I wanted to bring up the subject >> of a few of the ports that currently exist in the kos-ports >> tree. Specifically, there’s two that I’m pretty sure >> I’m going to get rid of and one that I’m considering >> doing away with. >> >> In the first category there, I’d like to get rid of libs3m >> and lwIP entirely from the kos-ports tree. libs3m doesn’t >> look like it’s worked in a long while (the code that >> actually gets turned into libs3m looks like it’s just a >> broken/old version of the snd_sfx_* code), so I don’t >> really think there’s going to be any objection there. >> lwIP, I’d like to get rid of because it has been >> completely superseded by the internal network stack. I know >> there are still a few performance related issues in the >> internal stack, but keeping lwIP around doesn’t really >> change that. So, if there aren’t any objections, I’m >> going to just do away with those two ports as I continue >> working on the new port manager. They’ll both continue to >> exist in the Git repositories they already have set up on >> the sourceforge page, I’m just planning on essentially >> acting like they don’t exist from now on. ;-) >> >> In the second category, I was wondering if anyone uses >> liboggvorbisplay over libtremor these days? libtremor has >> kinda been the “suggested” Vorbis library in KOS for a >> while, so I’m just wondering if it’s even worthwhile to >> keep liboggvorbisplay around. Any comments from anyone on >> that subject? >> >> I’ve rambled enough at this point, so I’ll cut this off >> here for now. Hopefully, I’ll have more good news on the >> new port management stuff very soon. :) >> >> - Lawrence >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across >> Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ >> applications >> Performance metrics, stats and reports that give you >> Actionable Insights >> Deep dive visibility with transaction tracing using APM >> Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y> >> _______________________________________________ >> cadcdev-kallistios mailing list >> cad...@li... <mailto:cad...@li...> >> https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios <https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios> >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y> >> _______________________________________________ >> cadcdev-kallistios mailing list >> cad...@li... >> https://lists.sourceforge.net/lists/listinfo/cadcdev-kallistios > |
