From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v2] meta-oe: recipes-graphics: add libvncserver recipe
Date: Tue, 13 Oct 2015 15:08:25 +0200 [thread overview]
Message-ID: <20151013130825.GE2396@jama> (raw)
In-Reply-To: <561CFBB4.4000404@ni.com>
[-- Attachment #1: Type: text/plain, Size: 2833 bytes --]
On Tue, Oct 13, 2015 at 03:40:20PM +0300, Ioan-Adrian Ratiu wrote:
> On 13.10.2015 13:53, Martin Jansa wrote:
> > On Fri, Oct 09, 2015 at 09:58:07AM +0300, Ioan-Adrian Ratiu wrote:
> >> Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
> >> ---
> >> .../libvncserver/libvncserver_0.9.10.bb | 19 +++++++++++++++++++
> >> 1 file changed, 19 insertions(+)
> >> create mode 100644 meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.10.bb
> >>
> >> diff --git a/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.10.bb b/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.10.bb
> >> new file mode 100644
> >> index 0000000..afa303c
> >> --- /dev/null
> >> +++ b/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.10.bb
> >> @@ -0,0 +1,19 @@
> >> +DESCRIPTION = "library for easy implementation of a RDP/VNC server"
Use SUMMARY for such short description.
> >> +HOMEPAGE = "https://libvnc.github.io"
> >> +SECTION = "libs"
> >> +PRIORITY = "optional"
Drop PRIORITY, we don't use it anywhere.
> >> +LICENSE = "GPLv2"
> >> +LIC_FILES_CHKSUM = "file://COPYING;md5=361b6b837cad26c6900a926b62aada5f"
> >> +
> >> +DEPENDS += "zlib jpeg libpng gtk+ libgcrypt nettle gnutls gmp"
> >> +RDEPENDS_${PN} += "libpng gtk+ libgcrypt"
> >> +
> >> +RCONFLICTS_${PN} = "x11vnc"
> >
> > This isn't enough to resolve conflicts with x11vnc in sysroot, this only
> > prevent installing both packages in the same image.
> >
> >> +
> >> +inherit autotools pkgconfig
> >> +
> >> +SRC_URI = "git://github.com/LibVNC/libvncserver.git;tag=LibVNCServer-0.9.10"
> >
> > Set SRCREV matching with this tag, otherwise bitbake will always use git
> > ls-remote to convert tag name to git SHA, which won't work for builds
> > from premirror (possibly without access to network)
> >
>
> This is easy to fix, however the above x11vnc conflict is not and I have
> to check with upstream developers which might take awhile.
>
> Is it ok to blacklist libvncserver in patch v3 in order to not break
> x11vnc until this is solved?
I don't want to introduce more blacklisted recipes in meta-oe, so this
won't be merged until it's resolved.
> >> +
> >> +S = "${WORKDIR}/git"
> >> +
> >> +EXTRA_OEMAKE_append=" SUBDIRS='libvncserver' "
> >> --
> >> 2.1.4
> >>
> >> --
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> >
> >
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-10-13 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 7:20 [meta-oe][PATCH] meta-oe: recipes-graphics: add libvncserver recipe Ioan-Adrian Ratiu
2015-10-08 10:08 ` Martin Jansa
2015-10-09 6:58 ` [meta-oe][PATCH v2] " Ioan-Adrian Ratiu
2015-10-13 10:53 ` Martin Jansa
2015-10-13 12:40 ` Ioan-Adrian Ratiu
2015-10-13 13:08 ` Martin Jansa [this message]
2015-10-14 10:53 ` Ioan-Adrian Ratiu
2015-10-14 14:06 ` Ioan-Adrian Ratiu
2015-10-14 14:16 ` Martin Jansa
2015-10-14 14:33 ` Ioan-Adrian Ratiu
2015-10-14 14:41 ` [OE-core] " Paul Eggleton
2015-10-14 14:43 ` Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151013130825.GE2396@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox