search for: libicecommon

Displaying 7 results from an estimated 7 matches for "libicecommon".

Did you mean: libibcommon
2004 Aug 06
0
proposal: new library, libicecommon
...'m wrong. It's a little more complicated than that, but essentially true. > my proposal is that we take all the icecast/ices shared modules (which > currently consist of AVL, HTTPP, LOG, NET, THREAD, TIMING) and bundle them > into a single library, which I propose to be called, libicecommon. This > library will be kept separately and will be required to be installed BEFORE > icecast is built. Similar to the dependency on libshout that ices has. I agree combining the helper modules makes sense. However, I'd suggest supporting a static link to a local build within the ic...
2004 Aug 06
0
proposal: new library, libicecommon
On Friday, 02 April 2004 at 22:19, oddsock wrote: > my proposal is that we take all the icecast/ices shared modules (which > currently consist of AVL, HTTPP, LOG, NET, THREAD, TIMING) and bundle them > into a single library, which I propose to be called, libicecommon. > This I agree with you up to this point - having all these tiny modules in one place would be a lot more convenient. > library will be kept separately and will be required to be installed BEFORE > icecast is built. Similar to the dependency on libshout that ices has. But I'm no...
2004 Aug 06
7
proposal: new library, libicecommon
...ot;check out" script which has the dependencies and directory requirements embedded in it.. my proposal is that we take all the icecast/ices shared modules (which currently consist of AVL, HTTPP, LOG, NET, THREAD, TIMING) and bundle them into a single library, which I propose to be called, libicecommon. This library will be kept separately and will be required to be installed BEFORE icecast is built. Similar to the dependency on libshout that ices has. This would add another library dependency to icecast (currently, we have dependencies for libcurl (optional), libxml2, pthread, libogg, and...
2004 Aug 06
0
proposal: new library, libicecommon
On Saturday 03 April 2004 14:19, oddsock wrote: > with our new move to Subversion, we apparently lost the ability to easily > link submodules into a single higher-level module (such as icecast)...in > the old CVS repository, icecast consisted of a handful of modules, > > icecast > and other modules, which are shared by icecast and ices : > avl httpp log net thread timing
2004 Aug 06
0
proposal: new library, libicecommon
At 10:46 PM 4/4/2004, you wrote: >This is what I meant by 'slightly more complicated than that'. > >We could use http: for read-write as well. This means using ssl >certificates for authentification. We didn't do that because everyone >already had ssh access set up and I didn't want to bother you all. >Aside from no one having written an ssl-agent, I can't
2004 Aug 06
2
proposal: new library, libicecommon
On Mon, Apr 05, 2004 at 11:49:45AM +1100, Michael Smith wrote: > I'm told (by Ralph) that subversion _does_ allow this, though it's not > currently set up. I'd prefer that solution, as it's simpler for users to > figure out. This is what I meant by 'slightly more complicated than that'. ubversion does have an auto-check-out-these-modules hack. It still treats
2004 Aug 06
1
proposal: new library, libicecommon
> > library will be kept separately and will be required to be installed BEFORE > > icecast is built. Similar to the dependency on libshout that ices has. > > But I'm not sure about this. There's nothing in those libraries of any > use to anything but icecast code itself, so I don't see why it should > be installed on users' systems. It's true that