incubator-bluesky-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "du.haipeng" <>
Subject Re: Re: Re: What should wo do next about the Bluesky Project?
Date Thu, 24 Jul 2008 01:51:56 GMT
While we were developing our project, we just included the libs which met our requirment. So
it took us a long time to list all of them.

Except XPlayer,which is based on mplayer, all the other part, components by components, are
by ourselves. 

GTk for user interface.

ffmpeg for audio video coding and decoding.

jrtp for transmitting multi media data.

artsd for sound play back.

jthread to achieve multi-thread.


and some system apis of linux.

===We started from scratch.===



发件人: Bernd Fondermann
发送时间: 2008-07-23 18:54:45
主题: Re: Re: What should wo do next about the Bluesky Project?

2008/7/23 chenwei_yi2003  < >:
> Maybe we should check the libs invoked in our Bluesky project .
> For LGPL,just dynamically call it ,and this is enough ;
> While for GPL,the best way to solve the problem is to substitute them with LGPL or recode
such libs ourselves.
> Can this work?

At first, really, you should focus on the code you actually intend to
move over into the ASF repository.
(The library aspect is only important after that.)

I know that I can download source code from the Bluesky website. But
where did _you_ actually get this code from at first (when the project
started or you started to develop specific components.) Can you give
URLs, please, where I can find the original code _before_ it entered
the BlueSky project.

If we cannot track down the origins of the code, there will be nothing
going into our repository, as far as I can tell.

By the way, I asked about the origins of you code multiple times now.
Do you understand, what I am talking about?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message