Re: [yocto] [meta-mingw][PATCH 2/2] cmake: add support for building nativesdk-cmake

2018-11-19 Thread Samuli Piippo 
Yeah, it was bad testing on my part, cmake really isn't ready for
prime-time until it works correctly from with the environment-setup
script.

I have enabled cmake on our sumo based SDK, where it works nicely with
the Qt Creator integration. It also builds there without the
winpthreads change. On thud, cmake was updated and now requires the
c++11 features from pthreads, which was more or less why I started
pushing these changes.

I'll update the patch and remove cmake from the packagegroup again.


On Mon, 19 Nov 2018 at 23:33, Joshua Watt  wrote:
>
>
>
> On Fri, Nov 16, 2018 at 12:33 AM Samuli Piippo  wrote:
>>
>> I've been testing cmake with Qt Creator integration which explicitly uses -G 
>> "MinGW Makefiles", while cmake defaults to NMake Makefiles. I'm not sure if 
>> it's possible to set generator in the toolchain file.
>
>
> Hmm, so perhaps Qt creator isn't using %CC% %CFLAGS% & friends? Did you 
> manually configure it to pass the right arguments to the compiler (e.g. path 
> to sysroot and such)? That might explain why it works for you since AFAIK, 
> cmake can't handle "\" as a path separator, and that is what our environment 
> setup script uses.
>
> I'm not specifically opposed to adding cmake to the SDK (I think it's 
> probably a good idea even), but if we are adding it to the default SDK 
> (nativesdk-packagegroup-sdk-host) I think it would be wise for it to work as 
> expected (e.g. work like it does in the Linux SDK). Fortunately, your patches 
> sent me off on a deeper tangent in my quest for automated testing of the 
> MinGW SDK, and I believe I have actually done a significant amount of the 
> work required to facilitate getting cmake working "as expected". You can take 
> a look at my patches on the jpew/oeqa branch in meta-mingw-contrib. For the 
> most part, the changes aren't too bad; the only one that really scares me is 
> the change to make the toolchain batch files use the unix path seperator (/) 
> instead of the Windows separator (\) ("classes/toolchain-scripts-mingw32: Use 
> Unix path separators"). I don't really know enough about cmake, so perhaps 
> there is some better (cmake specific) mechanism that we can use instead?
>
> Just to be clear, I don't mind the changes you made to make cmake build, but 
> I would prefer to not add it to the SDK by default until it actually works 
> with the SDK (and preferably has some test cases ;).
>
>
>>
>>
>> 
>> From: Joshua Watt 
>> Sent: 16 November 2018 05:35:50
>> To: Samuli Piippo
>> Cc: Yocto list discussion
>> Subject: Re: [yocto] [meta-mingw][PATCH 2/2] cmake: add support for building 
>> nativesdk-cmake
>>
>> On Thu, Nov 15, 2018 at 7:22 PM Samuli Piippo  wrote:
>> >
>> > Build nativesdk-cmake and dependency libs without without openssl.
>> >
>> > Signed-off-by: Samuli Piippo 
>> > ---
>> >  .../nativesdk-packagegroup-sdk-host.bbappend  | 1 +
>> >  recipes-devtools/cmake/cmake_%.bbappend   | 8 
>> >  recipes-extended/libarchive/libarchive_%.bbappend | 1 +
>> >  recipes-support/curl/curl_%.bbappend  | 2 ++
>> >  4 files changed, 12 insertions(+)
>> >  create mode 100644 recipes-devtools/cmake/cmake_%.bbappend
>> >  create mode 100644 recipes-extended/libarchive/libarchive_%.bbappend
>> >  create mode 100644 recipes-support/curl/curl_%.bbappend
>> >
>> > diff --git 
>> > a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend 
>> > b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
>> > index ad69b13..9544ffb 100644
>> > --- a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
>> > +++ b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
>> > @@ -2,4 +2,5 @@ RDEPENDS_${PN}_mingw32 = "\
>> >  nativesdk-pkgconfig \
>> >  nativesdk-libtool \
>> >  nativesdk-qemu \
>> > +nativesdk-cmake \
>>
>> Have you been successful at getting cmake to work properly in MinGW?
>> I've been working on automated tests for the SDK, and for kicks I
>> pulled in your changes and tried to write a test for cmake (heavily
>> borrowed from the cmake/assimp test in oe-core). When I ran the test,
>> I got the following:
>>
>> --- snip ---
>>
>> -- Building for: NMake Makefiles
>> -- The C compiler identification is GNU 8.2.0
>> CMake Error at 
>> Z:/projects/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage-sdk/CMakeTest-zljaq7x7/build/CMakeFiles/3.12.2/CMakeCCompiler.cmake:2
>> (set):
>>   Syntax error in cmake code at
>>
>> 
>> Z:/projects/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage-sdk/CMakeTest-zljaq7x7/build/CMakeFiles/3.12.2/CMakeCCompiler.cmake:2
>>
>>   when parsing string
>>
>>   -m32 -march=i586
>> --sysroot=Z:\projects\poky\build\tmp\work\QEMU~ELC\CORE~B5D\1N25.0-R\TEST~Y0Z\\sysroots\i586-poky-linux
>>
>>   Invalid escape sequence \p
>> Call Stack (most recent call first):
>>   CMakeLists.txt:38 (PROJECT)

[yocto] [layerindex-web][PATCH 00/30] Misc improvements (cover letter only)

2018-11-19 Thread Paul Eggleton 
A bunch of assorted improvements for the layer index.


The following changes since commit 24b6e13442c403ae6d4a2b1782a5b5f06b643e22:

  docker: add TASK_LOG_DIR to docker settings file (2018-10-04 11:15:39 +1300)

are available in the Git repository at:

  git://git.yoctoproject.org/layerindex-web paule/fixes11
  http://git.yoctoproject.org/cgit.cgi//log/?h=paule/fixes11

Paul Eggleton (30):
  Track and enable reporting on duplicate inc files
  Replace nvd3 with Chart.js
  update: handle if there is no origin/master branch in bitbake repo
  settings: add settings for CAPTCHA accessibility
  views: fix incorrect class usage in ClassSearchView
  Add CAPTCHA to registration/password reset forms
  Implement "delete account" function
  Allow user to edit their username in the Edit Profile form
  Restrict the number of username change attempts
  Use django-axes to lockout after multiple failed logins
  requirements.txt: update GitPython dependencies
  Add a script to help keep requirements.txt up to date
  Enable password strength validation by default
  Add some text to the password reset email
  Improve password form formatting
  Require re-registration if user changes email address
  Tweak activation complete page
  tools/github-fetch: handle non-fast-forward merges
  tools/github-fetch: fix marking deleted
  Exclude "Distro-specific" from "unknown/not available" in other distro search
  Use prop() instead of attr() to set checked property
  Replace uitablefilter usage with jQuery
  Add search to duplicates/comparison layer filter dialog
  Add search to layer dependencies list on edit/submit layer form
  README: add missing mention of TableSorter
  requirements.txt: bump versions
  Return to previous page after Edit profile
  Make login button return user to previous page
  Fix Submit/Edit layer form field rendering issue
  Fix drop-down alignment on duplicates page

 README| 6 +-
 TODO  | 1 -
 check_requirements.sh |39 +
 docker/settings.py|43 +-
 layerindex/admin.py   |10 +
 layerindex/auth_forms.py  |34 +
 layerindex/auth_views.py  |63 +
 layerindex/context_processors.py  | 5 +
 layerindex/forms.py   |28 +-
 layerindex/migrations/0026_incfile.py |24 +
 layerindex/models.py  |12 +
 layerindex/recipeparse.py | 4 +-
 layerindex/static/css/additional.css  | 7 +-
 layerindex/static/css/nv.d3.css   |   645 -
 layerindex/static/js/Chart.js | 14384 
 layerindex/static/js/Chart.min.js |10 +
 layerindex/static/js/d3.js|  9275 --
 layerindex/static/js/nv.d3.js | 14369 ---
 layerindex/static/js/uitablefilter.js |91 -
 layerindex/tools/github-fetch.py  | 6 +-
 layerindex/update.py  | 8 +-
 layerindex/update_layer.py|24 +-
 layerindex/views.py   |83 +-
 password_validation.py|25 +
 requirements.txt  |44 +-
 rrs/models.py | 2 +-
 rrs/static/js/uitablefilter.js|   117 -
 rrs/views.py  |22 +-
 settings.py   |43 +-
 templates/base.html   | 6 +-
 templates/layerindex/about.html   | 3 +-
 templates/layerindex/classicrecipes.html  |36 +-
 templates/layerindex/classicstats.html|70 +-
 templates/layerindex/deleteaccount.html   |56 +
 templates/layerindex/detail.html  |33 +-
 templates/layerindex/duplicates.html  |72 +-
 templates/layerindex/editlayer.html   |27 +-
 templates/layerindex/layerchecklist.html  | 2 +-
 templates/layerindex/layers.html  |83 +-
 templates/layerindex/profile.html | 5 +-
 .../registration/activation_complete.html | 8 +-
 templates/registration/login.html | 3 +
 .../registration/password_change_form.html|23 +-
 .../registration/password_reset_confirm.html  |23 +-
 .../registration/password_reset_done.html | 2 +-
 .../registration/password_reset_email.txt | 7 +-
 .../registration/password_reset_form.html |23 +-
 templates/registration/registration_form.html |23 +-
 templates/registration/reregister.html| 6 +
 templates/rrs/maintainers.html|13 +-
 templates/rrs/recipes.html| 6 +-
 templates/rrs/rrs_stats.html  |75 +-
 urls.py   |17 +-
 53

Re: [yocto] [meta-mingw][PATCH 2/2] cmake: add support for building nativesdk-cmake

2018-11-19 Thread Joshua Watt 
On Fri, Nov 16, 2018 at 12:33 AM Samuli Piippo  wrote:

> I've been testing cmake with Qt Creator integration which explicitly uses
> -G "MinGW Makefiles", while cmake defaults to NMake Makefiles. I'm not
> sure if it's possible to set generator in the toolchain file.
>

Hmm, so perhaps Qt creator isn't using %CC% %CFLAGS% & friends? Did you
manually configure it to pass the right arguments to the compiler (e.g.
path to sysroot and such)? That might explain why it works for you since
AFAIK, cmake can't handle "\" as a path separator, and that is what our
environment setup script uses.

I'm not specifically opposed to adding cmake to the SDK (I think it's
probably a good idea even), but if we are adding it to the default SDK (
nativesdk-packagegroup-sdk-host) I think it would be wise for it to work as
expected (e.g. work like it does in the Linux SDK). Fortunately, your
patches sent me off on a deeper tangent in my quest for automated testing
of the MinGW SDK, and I believe I have actually done a significant amount
of the work required to facilitate getting cmake working "as expected". You
can take a look at my patches on the jpew/oeqa branch in
meta-mingw-contrib. For the most part, the changes aren't too bad; the only
one that really scares me is the change to make the toolchain batch files
use the unix path seperator (/) instead of the Windows separator (\)
("classes/toolchain-scripts-mingw32: Use Unix path separators"). I don't
really know enough about cmake, so perhaps there is some better (cmake
specific) mechanism that we can use instead?

Just to be clear, I don't mind the changes you made to make cmake build,
but I would prefer to not add it to the SDK by default until it actually
works with the SDK (and preferably has some test cases ;).



>
> --
> *From:* Joshua Watt 
> *Sent:* 16 November 2018 05:35:50
> *To:* Samuli Piippo
> *Cc:* Yocto list discussion
> *Subject:* Re: [yocto] [meta-mingw][PATCH 2/2] cmake: add support for
> building nativesdk-cmake
>
> On Thu, Nov 15, 2018 at 7:22 PM Samuli Piippo  wrote:
> >
> > Build nativesdk-cmake and dependency libs without without openssl.
> >
> > Signed-off-by: Samuli Piippo 
> > ---
> >  .../nativesdk-packagegroup-sdk-host.bbappend  | 1 +
> >  recipes-devtools/cmake/cmake_%.bbappend   | 8 
> >  recipes-extended/libarchive/libarchive_%.bbappend | 1 +
> >  recipes-support/curl/curl_%.bbappend  | 2 ++
> >  4 files changed, 12 insertions(+)
> >  create mode 100644 recipes-devtools/cmake/cmake_%.bbappend
> >  create mode 100644 recipes-extended/libarchive/libarchive_%.bbappend
> >  create mode 100644 recipes-support/curl/curl_%.bbappend
> >
> > diff --git
> a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> > index ad69b13..9544ffb 100644
> > --- a/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> > +++ b/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bbappend
> > @@ -2,4 +2,5 @@ RDEPENDS_${PN}_mingw32 = "\
> >  nativesdk-pkgconfig \
> >  nativesdk-libtool \
> >  nativesdk-qemu \
> > +nativesdk-cmake \
>
> Have you been successful at getting cmake to work properly in MinGW?
> I've been working on automated tests for the SDK, and for kicks I
> pulled in your changes and tried to write a test for cmake (heavily
> borrowed from the cmake/assimp test in oe-core). When I ran the test,
> I got the following:
>
> --- snip ---
>
> -- Building for: NMake Makefiles
> -- The C compiler identification is GNU 8.2.0
> CMake Error at
> Z:/projects/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage-sdk/CMakeTest-zljaq7x7/build/CMakeFiles/3.12.2/CMakeCCompiler.cmake:2
> (set):
>   Syntax error in cmake code at
>
>
> Z:/projects/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/testimage-sdk/CMakeTest-zljaq7x7/build/CMakeFiles/3.12.2/CMakeCCompiler.cmake:2
>
>   when parsing string
>
>   -m32 -march=i586
>
> --sysroot=Z:\projects\poky\build\tmp\work\QEMU~ELC\CORE~B5D\1N25.0-R\TEST~Y0Z\\sysroots\i586-poky-linux
>
>   Invalid escape sequence \p
> Call Stack (most recent call first):
>   CMakeLists.txt:38 (PROJECT)
>
> --- snip ---
>
> It looks like cmake doesn't like the Windows style slashes in CFLAGS.
>
> You can see my test branch at jpew/oeqa in meta-mingw-contrib... it's
> still in progress so it might be a bit of work if you want to try it
> yourself.
>
> >  "
> > diff --git a/recipes-devtools/cmake/cmake_%.bbappend
> b/recipes-devtools/cmake/cmake_%.bbappend
> > new file mode 100644
> > index 000..f76cd82
> > --- /dev/null
> > +++ b/recipes-devtools/cmake/cmake_%.bbappend
> > @@ -0,0 +1,8 @@
> > +DEPENDS_remove_mingw32 = "ncurses"
> > +
> > +cmake_do_generate_toolchain_file_append_mingw32() {
> > +cat >> ${WORKDIR}/toolchain.cmake < > +set( CMAKE_SYSTEM_NAME Windows )
> > +EOF
> >

[yocto] [meta-mingw][PATCH v2 4/5] classes/toolchain-scripts-mingw32: Ensure exit code is success

2018-11-19 Thread Joshua Watt 
The "set" command in Windows has some unfortunate behaviors that can
frequently make it look like the toolchain script had an error. This
makes automated testing of the SDK more difficult, so add a line to the
environment setup script that ensures the script exits with success.

[YOCTO #13020]

Signed-off-by: Joshua Watt 
---
 classes/toolchain-scripts-mingw32.bbclass | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/classes/toolchain-scripts-mingw32.bbclass 
b/classes/toolchain-scripts-mingw32.bbclass
index a64f5f5..32493d7 100644
--- a/classes/toolchain-scripts-mingw32.bbclass
+++ b/classes/toolchain-scripts-mingw32.bbclass
@@ -81,6 +81,17 @@ toolchain_shared_env_script_sdkmingw32 () {
FOR %%x IN (%OECORE_NATIVE_SYSROOT%\\environment-setup.d\\*.bat) DO call 
"%%x"
 )
 EOF
+
+   # set has some annoying properties:
+   # 1) If it is successful %ERRORLEVEL% is unchanged (as opposed to being 
set
+   #to 0 to indicate success)
+   # 2) Making an assignment like "set A=" is considered an error and sets
+   #%ERRORLEVEL% to 1.
+   #
+   # Practically, this means that if any of the set calls make an empty
+   # assignment that error will be propagated. To prevent this, a command 
is
+   # run to ensure that the "exit code" of this script is 0
+   echo "@%COMSPEC% /C exit 0 > NUL" >> $script
 }
 
 toolchain_create_sdk_siteconfig_append_sdkmingw32 () {
-- 
2.19.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH v2 3/5] classes/toolchain-scripts-mingw32: Update variables

2018-11-19 Thread Joshua Watt 
Updates the variables configured by the toolchain script to match the
oe-core class. This combines the changes from:

0b5f1b0430 ("toolchain-scripts: put TARGET_ARCH and TARGET_OS into environment")
47160a8c51 ("cmake: fix linking in multilib SDKs")
668f56bb24 ("toolchain-scripts: drop PYTHONHOME")
81f126f4a8 ("toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME")

[YOCTO #13020]

Signed-off-by: Joshua Watt 
---
 classes/toolchain-scripts-mingw32.bbclass | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/classes/toolchain-scripts-mingw32.bbclass 
b/classes/toolchain-scripts-mingw32.bbclass
index b996a3e..a64f5f5 100644
--- a/classes/toolchain-scripts-mingw32.bbclass
+++ b/classes/toolchain-scripts-mingw32.bbclass
@@ -29,7 +29,9 @@ toolchain_create_sdk_env_script_sdkmingw32 () {
echo "set OECORE_NATIVE_SYSROOT=$sdkpathnative" >> $script
echo 'set OECORE_TARGET_SYSROOT=%SDKTARGETSYSROOT%' >> $script
echo "set OECORE_ACLOCAL_OPTS=-I $sdkpathnative/usr/share/aclocal" >> 
$script
-   echo "set PYTHONHOME=$sdkpathnative$prefix" >> $script
+   echo 'set OECORE_BASELIB=${baselib}' >> $script
+   echo 'set OECORE_TARGET_ARCH=${TARGET_ARCH}' >> $script
+   echo 'set OECORE_TARGET_OS=${TARGET_OS}' >> $script
 
toolchain_shared_env_script
 
-- 
2.19.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH v2 1/5] Add SDK test case framework

2018-11-19 Thread Joshua Watt 
Adds the framework for testing SDKs that ties into the oeqa test
framework. This allows commands like:

 $ bitbake -c testsdk ...

to be run for MinGW SDKs.

The test framework currently executes all tests under Wine in lieu of
having access to actual Windows machines.

[YOCTO #13020]

Signed-off-by: Joshua Watt 
---
 conf/machine-sdk/i686-mingw32.conf  |  1 +
 conf/machine-sdk/include/mingw32-common.inc |  7 ++
 conf/machine-sdk/x86_64-mingw32.conf|  1 +
 lib/oeqa/sdkmingw/__init__.py   |  0
 lib/oeqa/sdkmingw/case.py   | 87 +
 lib/oeqa/sdkmingw/cases/__init__.py |  0
 lib/oeqa/sdkmingw/context.py| 69 
 lib/oeqa/sdkmingw/testsdk.py| 42 ++
 8 files changed, 207 insertions(+)
 create mode 100644 lib/oeqa/sdkmingw/__init__.py
 create mode 100644 lib/oeqa/sdkmingw/case.py
 create mode 100644 lib/oeqa/sdkmingw/cases/__init__.py
 create mode 100644 lib/oeqa/sdkmingw/context.py
 create mode 100644 lib/oeqa/sdkmingw/testsdk.py

diff --git a/conf/machine-sdk/i686-mingw32.conf 
b/conf/machine-sdk/i686-mingw32.conf
index 5090168..fef48b5 100644
--- a/conf/machine-sdk/i686-mingw32.conf
+++ b/conf/machine-sdk/i686-mingw32.conf
@@ -1,3 +1,4 @@
 SDK_ARCH = "i686"
+TESTSDK_WINEARCH = "win32"
 
 require conf/machine-sdk/include/mingw32-common.inc
diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
index 733d092..71e8d45 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -26,6 +26,9 @@ SDKPKGSUFFIX = "nativesdk-mingw32"
 
 MACHINEOVERRIDES .= ":sdkmingw32"
 
+TESTSDK_CLASS_NAME = "oeqa.sdkmingw.testsdk.TestSDKMinGW"
+TESTSDKEXT_CLASS_NAME = ""
+
 WINDRES_mingw32 = "${HOST_PREFIX}windres --include-dir=${STAGING_INCDIR}"
 RC_mingw32 = "${WINDRES}"
 
@@ -39,3 +42,7 @@ DISABLE_STATIC_mingw32 = ""
 
 # disable security flags
 GCCPIE_mingw32 = ""
+
+# wine and wineserver are required to test MinGW SDKs
+HOSTTOOLS += "${@'wine wineserver' if (bb.utils.contains_any('IMAGE_CLASSES', 
'testsdk-mingw', True, False, d) or any(x in (d.getVar("BBINCLUDED") or "") for 
x in ["testsdk-mingw.bbclass"])) else ''}"
+
diff --git a/conf/machine-sdk/x86_64-mingw32.conf 
b/conf/machine-sdk/x86_64-mingw32.conf
index fc53822..188debc 100644
--- a/conf/machine-sdk/x86_64-mingw32.conf
+++ b/conf/machine-sdk/x86_64-mingw32.conf
@@ -1,3 +1,4 @@
 SDK_ARCH = "x86_64"
+TESTSDK_WINEARCH = "win64"
 
 require conf/machine-sdk/include/mingw32-common.inc
diff --git a/lib/oeqa/sdkmingw/__init__.py b/lib/oeqa/sdkmingw/__init__.py
new file mode 100644
index 000..e69de29
diff --git a/lib/oeqa/sdkmingw/case.py b/lib/oeqa/sdkmingw/case.py
new file mode 100644
index 000..169c143
--- /dev/null
+++ b/lib/oeqa/sdkmingw/case.py
@@ -0,0 +1,87 @@
+# Copyright 2018 by Garmin Ltd. or its subsidiaries
+# Released under the MIT license (see COPYING.MIT)
+
+import subprocess
+import os
+import tempfile
+import shutil
+import bb
+
+from oeqa.core.utils.path import remove_safe
+from oeqa.sdk.case import OESDKTestCase
+
+from oeqa.utils.subprocesstweak import errors_have_output
+errors_have_output()
+
+class OESDKMinGWTestCase(OESDKTestCase):
+def setUp(self):
+super().setUp()
+
+self.test_dir = tempfile.mkdtemp(prefix=self.__class__.__name__ + '-', 
dir=self.tc.sdk_dir)
+self.addCleanup(lambda: bb.utils.prunedir(self.test_dir))
+
+self.wine_test_dir = self.tc.wine_path(self.test_dir)
+
+def copyTestFile(self, src, dest=None):
+dest_path = dest or os.path.join(self.test_dir, os.path.basename(src))
+shutil.copyfile(src, dest_path)
+self.addCleanup(lambda: remove_safe(dest_path))
+
+def fetch(self, url, destdir=None, dl_dir=None, archive=None):
+if not destdir:
+destdir = self.test_dir
+
+if not dl_dir:
+dl_dir = self.td.get('DL_DIR', None)
+
+if not archive:
+from urllib.parse import urlparse
+archive = os.path.basename(urlparse(url).path)
+
+if dl_dir:
+tarball = os.path.join(dl_dir, archive)
+if os.path.exists(tarball):
+return tarball
+
+tarball = os.path.join(destdir, archive)
+subprocess.check_output(["wget", "-O", tarball, url])
+return tarball
+
+
+def _run(self, cmd):
+import shlex
+
+def strip_quotes(s):
+if s[0] == '"' and s[-1] == '"':
+return s[1:-1]
+return s
+
+command = ['wine', 'cmd', '/c', self.tc.wine_sdk_env, '>', 'NUL', 
'&&', 'cd', self.wine_test_dir, '&&']
+
+# Perform some massaging so that commands can be written naturally in
+# test cases. shlex.split() in Non-posix mode gets us most of the way
+# there, but it leaves the quotes around a quoted argument, so we
+# remove them manually.
+

[yocto] [meta-mingw][PATCH v2 2/5] Add .gitignore

2018-11-19 Thread Joshua Watt 
Adds a .gitignore which ignores python artifact files, as these are now
generated by the SDK tests

[YOCTO #13020]

Signed-off-by: Joshua Watt 
---
 .gitignore | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 .gitignore

diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..5da7ef5
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,3 @@
+*.pyc
+*.pyo
+
-- 
2.19.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH v2 0/5] Add oeqa test cases

2018-11-19 Thread Joshua Watt 
Adds the testing framework for tying tests for the MinGW SDK into the
oeqa SDK test framework. 

The SDK tests can be run using the standard SDK test command:

 bitbake -c testsdk 

All testing is done using Wine in lieu of having access to an actual
Windows machine. Wine is required to be installed on the host machine.

Joshua Watt (5):
  Add SDK test case framework
  Add .gitignore
  classes/toolchain-scripts-mingw32: Update variables
  classes/toolchain-scripts-mingw32: Ensure exit code is success
  oeqa/sdkmingw: Add test cases

 .gitignore  |  3 +
 classes/toolchain-scripts-mingw32.bbclass   | 15 +++-
 conf/machine-sdk/i686-mingw32.conf  |  1 +
 conf/machine-sdk/include/mingw32-common.inc |  7 ++
 conf/machine-sdk/x86_64-mingw32.conf|  1 +
 lib/oeqa/sdkmingw/__init__.py   |  0
 lib/oeqa/sdkmingw/case.py   | 87 +
 lib/oeqa/sdkmingw/cases/__init__.py |  0
 lib/oeqa/sdkmingw/cases/binutils.py | 55 +
 lib/oeqa/sdkmingw/cases/gcc.py  | 47 +++
 lib/oeqa/sdkmingw/cases/gdb.py  | 20 +
 lib/oeqa/sdkmingw/cases/pkgconfig.py| 18 +
 lib/oeqa/sdkmingw/context.py| 69 
 lib/oeqa/sdkmingw/files/testsdkmakefile |  4 +
 lib/oeqa/sdkmingw/testsdk.py| 42 ++
 15 files changed, 368 insertions(+), 1 deletion(-)
 create mode 100644 .gitignore
 create mode 100644 lib/oeqa/sdkmingw/__init__.py
 create mode 100644 lib/oeqa/sdkmingw/case.py
 create mode 100644 lib/oeqa/sdkmingw/cases/__init__.py
 create mode 100644 lib/oeqa/sdkmingw/cases/binutils.py
 create mode 100644 lib/oeqa/sdkmingw/cases/gcc.py
 create mode 100644 lib/oeqa/sdkmingw/cases/gdb.py
 create mode 100644 lib/oeqa/sdkmingw/cases/pkgconfig.py
 create mode 100644 lib/oeqa/sdkmingw/context.py
 create mode 100644 lib/oeqa/sdkmingw/files/testsdkmakefile
 create mode 100644 lib/oeqa/sdkmingw/testsdk.py

-- 
2.19.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] kconfig variables not being included in yocto build.

2018-11-19 Thread Bruce Ashfield 

On 2018-11-19 2:13 p.m., Sakib Sajal wrote:

Hello,

I have been trying to patch the linux kernel and add some kernel 
configuration but I am failing to add kconfig fragments to be included 
in the final build.


Initially I tried patching the kernel with hardcoded values in the patch.

I am building for qemu to minimize the variables I have to worry about.

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS    = "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-16.04"
TARGET_SYS   = "i586-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5.1"         // branch "sumo"
TUNE_FEATURES    = "m32 i586"
TARGET_FPU   = ""


My initial project structure:

-poky
--meta
--meta-poky
--meta-yocto-bsp
--meta-my-layer
---recipes-kernel
linux
-linux-yocto
--my-patch.patch
-linux-yocto_4%.bbappend
---conf
layer.conf

Content of the bbappend file:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += "file://my-patch.patch"

I enabled my-layer by adding the layer in the build/conf/bblayers.conf 
file. I was able to build an image and test my changes with the 
hardcoded valued in my patch.


However I want the values to be configurable through kernel 
configuration. Since I knew what variables I have introduced, I put them 
in a .cfg file with their desired values in the linux-yocto folder.


New project structure:

-poky
--meta-my-layer
---recipes-kernel
linux
-linux-yocto
--my-conf-frag.cfg

(other files and directories are same as before)

Added the following line to the .bbappend file:
SRC_URI += "file://my-conf-frag.cfg"

Content of my-conf-frag.cfg:
CONFIG_MY_FIRST_VAR="MY-NAME"
CONFIG_MY_SECOND_VAR=y

Then I run:
bitbake core-image-base

and get the following error:

ERROR: Task 
(/poky/meta/recipes-kernel/linux/linux-yocto_4.14.bb:do_compile) 
failed with exit code '1'


The kernel isn't being compiled since it does not know what 
"CONFIG_MY_FIRST_VAR" is.


I checked for .config files in the build directory and found one in 
"poky/build/tmp/work-shared/qemux86/kernel-source/.kernel-meta/cfg/.config" 
which contained the two variables I defined in my cfg file. But that 
file is a kernel configuration fragment file itself. The final config 
file which is used to build the image is located, I believe, in 
"poky/build/tmp/work/qemux86-poky-linux/linux-yocto/4.14.67+gitAUTOINC+c43c9e19a2_084af9624d-r0/linux-qemux86-standard-build/.config" 
but i do not see the variables there in the final .config file. I was 
also able to locate the cfg and the patch file in 
"/poky/build/tmp/work/qemux86-poky-linux/linux-yocto/4.14.67+gitAUTOINC+c43c9e19a2_084af9624d-r0/"directory. 
Therefore the files are being picked up by the build system but the 
fragments are not being applied to make the final .config file used to 
build the kernel.


Without being able to see the code that defines those CONFIG_
symbols, I can't say for sure. But if the fragment was located
and added to the config queue, then the only real way that they
wouldn't be in the final .config is a missing dependency for the
option.

If there's any way that you could make the specific layers available
to me for a test build, I could offer more specific suggestions.

Bruce



I went through yocto mailing list for similar problems and followed the 
steps provided with no success. I also went through yocto's mega-manual 
and kernel development manual as well as the yocto-lab pdfs and followed 
all the different steps but i always get the compilation error.


Can someone please help me. Thanks in advance!

Sakib Sajal




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [[yocto-docs][thud][PATCH] ref-system-requirements: sync with thud poky.conf

2018-11-19 Thread Scott Rifenbark 
Thanks Armin!  You too!

On Mon, Nov 19, 2018 at 11:28 AM akuster808  wrote:

>
>
> On 11/19/18 10:16 AM, Scott Rifenbark wrote:
>
> Armin,
>
> See
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros
> and let me know if the patch is good.
>
> Looks good.
> Thanks,
> Have a good Thanksgiving.
> Armin
>
>
> Thanks,
> Scott
>
> On Sun, Nov 18, 2018 at 6:15 PM Armin Kuster  wrote:
>
>> poky.conf
>> ubuntu-16.04
>> ubuntu-16.10
>> ubuntu-17.04
>> fedora-26
>> centos-7
>> debian-8
>> debian-9
>> opensuse-42.1
>> opensuse-42.2
>>
>> Signed-off-by: Armin Kuster 
>> ---
>>  documentation/ref-manual/ref-system-requirements.xml | 20
>> 
>>  1 file changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/documentation/ref-manual/ref-system-requirements.xml
>> b/documentation/ref-manual/ref-system-requirements.xml
>> index 9298e84..0abc47e 100644
>> --- a/documentation/ref-manual/ref-system-requirements.xml
>> +++ b/documentation/ref-manual/ref-system-requirements.xml
>> @@ -93,19 +93,22 @@
>>  Ubuntu 11.10
>>  Ubuntu 12.04 (LTS)
>>  Ubuntu 13.10
>> -Ubuntu 14.04 (LTS) -->
>> +Ubuntu 14.04 (LTS)
>>  Ubuntu 14.10
>>  Ubuntu 15.04
>> -Ubuntu 15.10
>> +Ubuntu 15.10 -->
>>  Ubuntu 16.04 (LTS)
>> +Ubuntu 16.10 (LTS)
>> +Ubuntu 17.04 
>>  
>> +Fedora release 20
>> (Heisenbug)
>>  Fedora release 22
>>  Fedora release 23
>> -
>> +Fedora release 26
>> +
>> -
>> -openSUSE 13.2
>> +openSUSE 13.1
>> +openSUSE 13.2 -->
>>  openSUSE 42.1
>> +openSUSE 42.2
>>  
>>  
>>
>> --
>> 2.7.4
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [[yocto-docs][thud][PATCH] ref-system-requirements: sync with thud poky.conf

2018-11-19 Thread akuster808 


On 11/19/18 10:16 AM, Scott Rifenbark wrote:
> Armin,
>
> See
> https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros
> and let me know if the patch is good.
Looks good.
Thanks,
Have a good Thanksgiving.
Armin
>
> Thanks,
> Scott
>
> On Sun, Nov 18, 2018 at 6:15 PM Armin Kuster  > wrote:
>
> poky.conf
>     ubuntu-16.04
>     ubuntu-16.10
>     ubuntu-17.04
>     fedora-26
>     centos-7
>     debian-8
>     debian-9
>     opensuse-42.1
>     opensuse-42.2
>
> Signed-off-by: Armin Kuster  >
> ---
>  documentation/ref-manual/ref-system-requirements.xml | 20
> 
>  1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/documentation/ref-manual/ref-system-requirements.xml
> b/documentation/ref-manual/ref-system-requirements.xml
> index 9298e84..0abc47e 100644
> --- a/documentation/ref-manual/ref-system-requirements.xml
> +++ b/documentation/ref-manual/ref-system-requirements.xml
> @@ -93,19 +93,22 @@
>                  Ubuntu 11.10
>                  Ubuntu 12.04 (LTS)
>                  Ubuntu 13.10
> -                Ubuntu 14.04
> (LTS) -->
> +                Ubuntu 14.04 (LTS)
>                  Ubuntu 14.10
>                  Ubuntu 15.04
> -                Ubuntu 15.10
> +                Ubuntu 15.10 -->
>                  Ubuntu 16.04 (LTS)
> +                Ubuntu 16.10 (LTS)
> +                Ubuntu 17.04 
>  
> +                Fedora release 20
> (Heisenbug)
>                  Fedora release 22
>                  Fedora release 23
> -
> +                Fedora release 26
> +
> -
> -                openSUSE 13.2
> +                openSUSE 13.1
> +                openSUSE 13.2 -->
>                  openSUSE 42.1
> +                openSUSE 42.2
>              
>          
>
> -- 
> 2.7.4
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] kconfig variables not being included in yocto build.

2018-11-19 Thread Sakib Sajal 
Hello,

I have been trying to patch the linux kernel and add some kernel configuration 
but I am failing to add kconfig fragments to be included in the final build.

Initially I tried patching the kernel with hardcoded values in the patch.

I am building for qemu to minimize the variables I have to worry about.

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "ubuntu-16.04"
TARGET_SYS   = "i586-poky-linux"
MACHINE  = "qemux86"
DISTRO   = "poky"
DISTRO_VERSION   = "2.5.1" // branch "sumo"
TUNE_FEATURES= "m32 i586"
TARGET_FPU   = ""


My initial project structure:

-poky
--meta
--meta-poky
--meta-yocto-bsp
--meta-my-layer
---recipes-kernel
linux
-linux-yocto
--my-patch.patch
-linux-yocto_4%.bbappend
---conf
layer.conf

Content of the bbappend file:
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"

SRC_URI += "file://my-patch.patch"

I enabled my-layer by adding the layer in the build/conf/bblayers.conf file. I 
was able to build an image and test my changes with the hardcoded valued in my 
patch.

However I want the values to be configurable through kernel configuration. 
Since I knew what variables I have introduced, I put them in a .cfg file with 
their desired values in the linux-yocto folder.

New project structure:

-poky
--meta-my-layer
---recipes-kernel
linux
-linux-yocto
--my-conf-frag.cfg

(other files and directories are same as before)

Added the following line to the .bbappend file:
SRC_URI += "file://my-conf-frag.cfg"

Content of my-conf-frag.cfg:
CONFIG_MY_FIRST_VAR="MY-NAME"
CONFIG_MY_SECOND_VAR=y

Then I run:
bitbake core-image-base

and get the following error:

ERROR: Task 
(/poky/meta/recipes-kernel/linux/linux-yocto_4.14.bb:do_compile) 
failed with exit code '1'

The kernel isn't being compiled since it does not know what 
"CONFIG_MY_FIRST_VAR" is.

I checked for .config files in the build directory and found one in 
"poky/build/tmp/work-shared/qemux86/kernel-source/.kernel-meta/cfg/.config" 
which contained the two variables I defined in my cfg file. But that file is a 
kernel configuration fragment file itself. The final config file which is used 
to build the image is located, I believe, in 
"poky/build/tmp/work/qemux86-poky-linux/linux-yocto/4.14.67+gitAUTOINC+c43c9e19a2_084af9624d-r0/linux-qemux86-standard-build/.config"
 but i do not see the variables there in the final .config file. I was also 
able to locate the cfg and the patch file in 
"/poky/build/tmp/work/qemux86-poky-linux/linux-yocto/4.14.67+gitAUTOINC+c43c9e19a2_084af9624d-r0/"directory.
 Therefore the files are being picked up by the build system but the fragments 
are not being applied to make the final .config file used to build the kernel.

I went through yocto mailing list for similar problems and followed the steps 
provided with no success. I also went through yocto's mega-manual and kernel 
development manual as well as the yocto-lab pdfs and followed all the different 
steps but i always get the compilation error.

Can someone please help me. Thanks in advance!

Sakib Sajal

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [[yocto-docs][thud][PATCH] ref-system-requirements: sync with thud poky.conf

2018-11-19 Thread Scott Rifenbark 
Armin,

See
https://yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#detailed-supported-distros
and let me know if the patch is good.

Thanks,
Scott

On Sun, Nov 18, 2018 at 6:15 PM Armin Kuster  wrote:

> poky.conf
> ubuntu-16.04
> ubuntu-16.10
> ubuntu-17.04
> fedora-26
> centos-7
> debian-8
> debian-9
> opensuse-42.1
> opensuse-42.2
>
> Signed-off-by: Armin Kuster 
> ---
>  documentation/ref-manual/ref-system-requirements.xml | 20
> 
>  1 file changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/documentation/ref-manual/ref-system-requirements.xml
> b/documentation/ref-manual/ref-system-requirements.xml
> index 9298e84..0abc47e 100644
> --- a/documentation/ref-manual/ref-system-requirements.xml
> +++ b/documentation/ref-manual/ref-system-requirements.xml
> @@ -93,19 +93,22 @@
>  Ubuntu 11.10
>  Ubuntu 12.04 (LTS)
>  Ubuntu 13.10
> -Ubuntu 14.04 (LTS) -->
> +Ubuntu 14.04 (LTS)
>  Ubuntu 14.10
>  Ubuntu 15.04
> -Ubuntu 15.10
> +Ubuntu 15.10 -->
>  Ubuntu 16.04 (LTS)
> +Ubuntu 16.10 (LTS)
> +Ubuntu 17.04 
>  
> +Fedora release 20
> (Heisenbug)
>  Fedora release 22
>  Fedora release 23
> -
> +Fedora release 26
> +
> -
> -openSUSE 13.2
> +openSUSE 13.1
> +openSUSE 13.2 -->
>  openSUSE 42.1
> +openSUSE 42.2
>  
>  
>
> --
> 2.7.4
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Unassigned Bugs - Help Needed

2018-11-19 Thread Jolley, Stephen K 
All,



The triage team meets weekly and does its best to handle the bugs reported into 
the bugzilla. The number of people attending that meeting has fallen, as have 
the number of people available to help fix bugs. One of the things we hear 
users report is they don't know how to help. We (the triage team) are therefore 
going to start reporting out the currently 297 unassigned bugs.



We're hoping people may be able to spare some time now and again to help out 
with these.



Bugs are split into two types, "true bugs" where things don't work as they 
should and "enhancements" which are features we'd want to add to the system.



There are also roughly four different "priority" classes right now, "2.7", 
"2.8", "2.99" and "Future", the more pressing/urgent issues being in "2.7" and 
then "2.8".



Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me 
(stephen.k.jol...@intel.com) an e-mail with 
the bug number you would like and I will assign it to you (please make sure you 
have a bugzilla account).



The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] CAN: Add Pican2 support

2018-11-19 Thread Andrei Gherzan 
Hi Fabien,

On Fri, Nov 16, 2018 at 5:29 PM Fabien Lahoudere <
fabien.lahoud...@collabora.com> wrote:

> In order to make Pican 2 work, we :
> - add mcp2515.dto to the overlay list
> - add a variable to enable it in local.conf
> - create a udev rule to mount interface
>

>
> http://skpang.co.uk/catalog/pican2-canbus-board-for-raspberry-pi-23-p-1475.html
>
> Signed-off-by: Fabien Lahoudere 
>

Could you please submit this PR in github? Check the readme for more
information.
--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Modify login prompt with script output

2018-11-19 Thread Donal Morrissey 
Hi There,
Is it possible to modify the login prompt so that it includes the output of
a script?
I know I can modify the /etc/issue file as part of the build to include
custom text, but I would like to have a script which is executed to
generate some text to be displayed as part of the prompt.
Cheers,
Donal
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-docs][thud][v2][PATCH] ref-system-requirements: sync with thud poky.conf

2018-11-19 Thread akuster 


On 11/19/18 2:44 AM, Bas Mevissen wrote:
> On 2018-11-19 04:08, Armin Kuster wrote:
>> poky.conf
>>     ubuntu-16.04
>>     ubuntu-16.10
>>     ubuntu-17.04
>>     fedora-26
>
> Support for Fedora 26 has ended. I've been using Fedora 27 and 28 for
> Sumo and they are fine for me. I can do some tests on Thud. However, I
> cannot do the full 2TB tests that are suggested at
> https://wiki.yoctoproject.org/wiki/Distribution_Support and
> https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan
Thanks for the info. I believe the Test plan has been superseded by the
builders bring up in the AutoBuilder. The version in master has been
updated so you make want to take a look.

I am aligning the Docs with what is identified in the Thud released
sources. The becomes our stake in the ground. As time goes on we test on
newer host OS and update accordingly.

Thanks
- armin
>
> -- Bas.
>
>>     centos-7
>>     debian-8
>>     debian-9
>>     opensuse-42.1
>>     opensuse-42.2
>>
>> Signed-off-by: Armin Kuster 
>>
>> -- 
>> [v2]
>> Drop LTS for ubuntu-16.10
>> ---
>>  documentation/ref-manual/ref-system-requirements.xml | 20
>> 
>>  1 file changed, 12 insertions(+), 8 deletions(-)
>>
>> diff --git a/documentation/ref-manual/ref-system-requirements.xml
>> b/documentation/ref-manual/ref-system-requirements.xml
>> index 9298e84..6795a69 100644
>> --- a/documentation/ref-manual/ref-system-requirements.xml
>> +++ b/documentation/ref-manual/ref-system-requirements.xml
>> @@ -93,19 +93,22 @@
>>  Ubuntu 11.10
>>  Ubuntu 12.04 (LTS)
>>  Ubuntu 13.10
>> -    Ubuntu 14.04 (LTS)
>> -->
>> +    Ubuntu 14.04 (LTS)
>>  Ubuntu 14.10
>>  Ubuntu 15.04
>> -    Ubuntu 15.10
>> +    Ubuntu 15.10 -->
>>  Ubuntu 16.04 (LTS)
>> +    Ubuntu 16.10 
>> +    Ubuntu 17.04 
>>  
>> +    Fedora release 20
>> (Heisenbug)
>>  Fedora release 22
>>  Fedora release 23
>> -
>> +    Fedora release 26
>> +
>> -
>> -    openSUSE 13.2
>> +    openSUSE 13.1
>> +    openSUSE 13.2 -->
>>  openSUSE 42.1
>> +    openSUSE 42.2
>>  
>>  
>>
>> -- 
>> 2.7.4
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-docs][thud][v2][PATCH] ref-system-requirements: sync with thud poky.conf

2018-11-19 Thread Bas Mevissen 

On 2018-11-19 04:08, Armin Kuster wrote:

poky.conf
ubuntu-16.04
ubuntu-16.10
ubuntu-17.04
fedora-26


Support for Fedora 26 has ended. I've been using Fedora 27 and 28 for 
Sumo and they are fine for me. I can do some tests on Thud. However, I 
cannot do the full 2TB tests that are suggested at 
https://wiki.yoctoproject.org/wiki/Distribution_Support and 
https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan


-- Bas.


centos-7
debian-8
debian-9
opensuse-42.1
opensuse-42.2

Signed-off-by: Armin Kuster 

--
[v2]
Drop LTS for ubuntu-16.10
---
 documentation/ref-manual/ref-system-requirements.xml | 20 


 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/documentation/ref-manual/ref-system-requirements.xml
b/documentation/ref-manual/ref-system-requirements.xml
index 9298e84..6795a69 100644
--- a/documentation/ref-manual/ref-system-requirements.xml
+++ b/documentation/ref-manual/ref-system-requirements.xml
@@ -93,19 +93,22 @@
 Ubuntu 11.10
 Ubuntu 12.04 (LTS)
 Ubuntu 13.10
-Ubuntu 14.04 (LTS) 
-->

+Ubuntu 14.04 (LTS)
 Ubuntu 14.10
 Ubuntu 15.04
-Ubuntu 15.10
+Ubuntu 15.10 -->
 Ubuntu 16.04 (LTS)
+Ubuntu 16.10 
+Ubuntu 17.04 
 
+Fedora release 20
(Heisenbug)
 Fedora release 22
 Fedora release 23
-

+Fedora release 26
+
-
-openSUSE 13.2
+openSUSE 13.1
+openSUSE 13.2 -->
 openSUSE 42.1
+openSUSE 42.2
 
 

--
2.7.4


--
Bas.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Need Support- Variable exporting

2018-11-19 Thread bhuvana easwari 
Hi,

I need support on the below issue.

1) Actually we are trying to build two machine from one meta-layer based on
some choice.
2) Both devices having different configuration files.
3) Now we have to export a variable from machine configuration conf file to
layer.conf
4) Based on the exported variable value,we are choosing device specific
conf file.

Can you please give some input on this

Regards,
Bhuvaneswari K
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto