6:02 p.m.
Hi guys,
I have integrated this media-service-upnp in my project but I suddenly saw
this dleyna-server project seems to do the same according the descriptions
in the following pages:
https://01.org/dleyna/documentation/dleyna-server
https://github.com/01org/media-service-upnp/blob/master/README
Even though when I tried to install the dleyna-server the gupnp version
required is higher. Also, media-service-upnp seems not to need the
dleyna-core at all but only the gupnp stack.
As I said, the API seems to be the same (and does the same?), or are there
differences?
Thanks and regards!
9:44 p.m.
On 01/03/2015 09:02 AM, Linux mail wrote:
I have integrated this media-service-upnp in my project but I
suddenly
saw this dleyna-server project seems to do the same according the
descriptions in the following pages:
https://01.org/dleyna/documentation/dleyna-server
https://github.com/01org/media-service-upnp/blob/master/README
Even though when I tried to install the dleyna-server the gupnp version
required is higher. Also, media-service-upnp seems not to need the
dleyna-core at all but only the gupnp stack.
As I said, the API seems to be the same (and does the same?), or are
there differences?
Note that the last commit date in media-service-upnp is roughly same as
first commit date in dleyna-server. :)
I think at some point media-service-upnp was renamed to dleyna-server
and moved to the new repository, so you should really update to the latter.
Alex
3:35 a.m.
Hi Alexander,
Thank you very much for your answer! Right now I have upgraded the gupnp
package and installed the latest dleyna-core but now that I try to get the
dleyna-server alone (this is, without the dleyna-connector-dbus) I see it
tries to install the dbus services anyway.
I read in the dleyna-server page
<https://01.org/dleyna/documentation/dleyna-server> the following:
*"dLeyna-server itself is not bound to a particular IPC mechanism and its
flexible architecture permits the use of different IPC mechanisms via
dynamically loaded modules called connectors. Currently, only one such
module exists, dLeyna-connector-dbus."*
So my question is, Can I install the dleyna-server without the
dleyna-connector-dbus? If not, Can I add a dleyna-connector-xxx along
with dleyna-connector-dbus?
As a comment, my system uses sockets as IPC so I plan to attach a socket
server to the dleyna-server.
Thanks and regards,
Lucio
On Tue, Jan 13, 2015 at 4:44 AM, Alexander Kanavin <
alexander.kanavin(a)intel.com> wrote:
On 01/03/2015 09:02 AM, Linux mail wrote:
> I have integrated this media-service-upnp in my project but I suddenly
> saw this dleyna-server project seems to do the same according the
> descriptions in the following pages:
> https://01.org/dleyna/documentation/dleyna-server
> https://github.com/01org/media-service-upnp/blob/master/README
> Even though when I tried to install the dleyna-server the gupnp version
> required is higher. Also, media-service-upnp seems not to need the
> dleyna-core at all but only the gupnp stack.
> As I said, the API seems to be the same (and does the same?), or are
> there differences?
>
Note that the last commit date in media-service-upnp is roughly same as
first commit date in dleyna-server. :)
I think at some point media-service-upnp was renamed to dleyna-server and
moved to the new repository, so you should really update to the latter.
Alex
_______________________________________________
dLeyna mailing list
dLeyna(a)lists.01.org
https://lists.01.org/mailman/listinfo/dleyna
3:03 a.m.
On 01/13/2015 06:35 PM, Linux mail wrote:
Thank you very much for your answer! Right now I have upgraded the
gupnp
package and installed the latest dleyna-core but now that I try to get
the dleyna-server alone (this is, without the dleyna-connector-dbus) I
see it tries to install the dbus services anyway.
Please provide more details about what are you doing and what happens.
If you try to compile dleyna-server from source, then it will not
require dleyna-connector-dbus. Then, before you run it you need to
specify the connector name in the config file (that name is 'dbus' by
default).
I read in the dleyna-server page
<https://01.org/dleyna/documentation/dleyna-server> the following:
/"dLeyna-server itself is not bound to a particular IPC mechanism and
its flexible architecture permits the use of different IPC mechanisms
via dynamically loaded modules called connectors. Currently, only one
such module exists, dLeyna-connector-dbus."/
So my question is, Can I install the dleyna-server without the
dleyna-connector-dbus? If not, Can I add a dleyna-connector-xxx along
with dleyna-connector-dbus?
As a comment, my system uses sockets as IPC so I plan to attach a socket
server to the dleyna-server.
You need to provide more details about how are you attempting to install
dleyna-server. If you are compiling it from source, there should be no
dbus dependency of any kind.
Alex
2:33 a.m.
On Wed, Jan 14, 2015 at 10:03 AM, Alexander Kanavin <
alexander.kanavin(a)intel.com> wrote:
On 01/13/2015 06:35 PM, Linux mail wrote:
Thank you very much for your answer! Right now I have upgraded the gupnp
> package and installed the latest dleyna-core but now that I try to get
> the dleyna-server alone (this is, without the dleyna-connector-dbus) I
> see it tries to install the dbus services anyway.
>
Please provide more details about what are you doing and what happens.
If you try to compile dleyna-server from source, then it will not require
dleyna-connector-dbus. Then, before you run it you need to specify the
connector name in the config file (that name is 'dbus' by default).
I'm adding dleyna-server to a Yocto distro. The recipe is pretty much the
same as the media_service_upnp
<https://github.com/openembedded/meta-oe/blob/master/meta-multimedia/recip...
(I changed LIC_FILES_CHKSUM and SRCREV to match dleyna-core/server, as well
as erased dms-info installation), so yes, I´m compiling from source.
The output I *was* seeing is this:
WARNING: QA Issue: dleyna-server: Files/directories were installed but not
shipped
/usr/share
/usr/bin
/usr/share/dbus-1
/usr/share/dbus-1/services
/usr/share/dbus-1/services/com.intel.dleyna-server.service
ERROR: QA Issue: non -dev/-dbg/-nativesdk package contains symlink .so:
dleyna-server path
'/work/cortexa15hf-vfp-neon-3.10-oe-linux-gnueabi/dleyna-server/0.5.0-r1/packages-split/dleyna-server/usr/lib/dleyna-server/
libdleyna-server-1.0.so'
As you can see, it installs the dbus service (I can even see it in the
sysroot) so I thought the issue was because of the dbus connector not being
installed but I noticed the error is because of the shared object. Doing a
bit of google I found I need to redirect the files into the correct package
by doing: FILES_${PN} = "${libdir}/lib*.so"
Nevertheless, as you pointed out, the default connector is dbus so I will
need to change it to socket server connector in the config file.
Thank you very much!
Lucio
2803
days inactive
2815
days old
4 comments
2 participants
participants (2)
-
Alexander Kanavin -
Linux mail