All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Nelson, Sam" <sam.nelson@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
	"Cooper Jr., Franklin" <fcooper@ti.com>
Subject: Re: [PATCH] branding-mcsdk: Adding MCSDK branding include file
Date: Thu, 19 Feb 2015 21:55:58 -0500	[thread overview]
Message-ID: <20150220025557.GG31287@edge> (raw)
In-Reply-To: <4F9216F96E5DF9428610502835A9F49058110B5F@DLEE11.ent.ti.com>

Coming back to this discussion...


On Fri, Feb 06, 2015 at 09:29:48PM -0500, Nelson, Sam wrote:
> > > > > > > - To control preferred version and providers for MCSDK
> > > > > > >
> > > > > > > Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> > > > > > > ---
> > > > > > >  .../conf/distro/include/branding-mcsdk.inc         |   20
> > > > > > ++++++++++++++++++++
> > > > > > >  1 file changed, 20 insertions(+)  create mode 100644
> > > > > > > meta-arago-distro/conf/distro/include/branding-
> > > > > > mcsdk.inc
> > > > > > >
> > > > > > > diff --git
> > > > > > > a/meta-arago-distro/conf/distro/include/branding-mcsdk.inc
> > > > > > b/meta-arago-distro/conf/distro/include/branding-mcsdk.inc
> > > > > > > new file mode 100644
> > > > > > > index 0000000..d023b67
> > > > > > > --- /dev/null
> > > > > > > +++ b/meta-arago-distro/conf/distro/include/branding-mcsdk.inc
> > > > > > > @@ -0,0 +1,20 @@
> > > > > > > +# MCSDK branding configuration
> > > > > > > +
> > > > > > > +# Use the MCSDK supported versions PREFERRED_VERSION_libnl =
> > > > > > > +"3.2.24"
> > > > > > > +
> > > > > > > +DISTRO_FEATURES += "x11 opengl"
> > > > > >
> > > > > > I assume x11 is to make Java happy? I don't think you have x11 env...
> > > > > >
> > > > > [Sam] Yes it was to make Java happy.
> > > > [Franklin] I thought I remembered that the mcsdk were meant for headless
> > > devices.
> > > > If so I would recommend taking a look at the discussion here:
> > > > https://github.com/woglinde/meta-java/issues/45
> > > >
> > > > Pulling in x11 and gtk seems painful especially since you're not using it.
> > > > Anyway it's something to look into if it is indeed meant for headless
> > devices.
> > > > But its ur branding file so my above comments aren't meant to block this
> > > patch from being accepted.
> > >
> > > Well, as explained in that tracker link you provided, pulling X libs for the
> > build
> > > doesn't necessary mean you'll end up with X component on the target.
> > > Yes, disabling AWT is a nice touch, hopefully it gets integrated into meta-
> > java
> > [Franklin] Maybe for the very specific x11 recipes but pulling the generic gtk+
> > package I'm not sure things will end up being as lucky. The changes
> > mentioned in the link specifically drops the gtk dependency. Also adding X11
> > to your distro features I'm assuming will affect quite a bit of recipes that may
> > pull in additional x11 dependencies that they may have avoided otherwise.
> > 
> > Anyway I was making assumptions so if that isn't occurring in their current
> > builds feel free to ignore my crazy rambling :)

> [Sam] I tried the patch mentioned in tracker link. But I see libxt 
> libxinerama libxrender all depend on x11.
> So not giving anything useful.

But according to the comments, it skips building AWT and removes GTK 
dependencies. Plus the build is faster. Do you want to include it?

I'm wondering if libxt, libxinerama and libxrender require 
DISTRO_FEATURES += "x11"...


> > > > > > > +# Java preferences.
> > > > > > > +#PREFERRED_VERSION_openjdk-7-jre = "25b30-2.3.12"
> > > > > > > +PREFERRED_VERSION_icedtea7-native = "2.1.3"
> > > > > > > +PREFERRED_PROVIDER_openjdk-7-jre = "openjdk-7-jre"
> > > > > > > +
> > > > > > > +PREFERRED_PROVIDER_virtual/java-initial = "cacao-initial"
> > > > > > > +
> > > > > > > +PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
> > > > > > > +PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
> > > > > > > +
> > > > > > > +PREFERRED_PROVIDER_jpeg-native = "jpeg-native"
> > > > > > > +#PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"
> > > > > > > +PREFERRED_PROVIDER_glibc-gconv-iso8859-1 = "nativesdk-eglibc-
> > > locale"
> > > > > > > --
> > > > > > > 1.7.9.5
> > > > > > >
> > > > > > > _______________________________________________
> > > > > > > meta-arago mailing list
> > > > > > > meta-arago@arago-project.org
> > > > > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> > > > > _______________________________________________
> > > > > meta-arago mailing list
> > > > > meta-arago@arago-project.org
> > > > > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago


  reply	other threads:[~2015-02-20  2:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 18:54 [PATCH] branding-mcsdk: Adding MCSDK branding include file Sam Nelson
2015-02-06 18:59 ` Cooper Jr., Franklin
2015-02-06 19:50   ` Nelson, Sam
2015-02-06 18:59 ` Denys Dmytriyenko
2015-02-06 19:51   ` Nelson, Sam
2015-02-06 20:32     ` Cooper Jr., Franklin
2015-02-06 20:42       ` Denys Dmytriyenko
2015-02-06 21:07         ` Cooper Jr., Franklin
2015-02-07  2:29           ` Nelson, Sam
2015-02-20  2:55             ` Denys Dmytriyenko [this message]
2015-02-20  4:26               ` Nelson, Sam
2015-02-06 20:30 ` Denys Dmytriyenko
2015-02-06 21:04   ` Nelson, Sam
2015-02-06 21:21     ` Denys Dmytriyenko

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=20150220025557.GG31287@edge \
    --to=denys@ti.com \
    --cc=fcooper@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=sam.nelson@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.