On 02/09/2018 07:43 AM, Chang Rebecca Swee Fun wrote:
Settings mentioned in the README have been ported over and now users
are able to copy and start modifying for personal use cases.
This file will served as a reference to minimize errors when users
trying to create a new conf file by following
Oops, please proceed to make the changes, on both README and commit message.
Thanks,
Rebecca
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Alexander Kanavin
> Sent: Friday, February 9, 2018 3:15 PM
> To: yocto@yoctoproj
On 02/09/2018 02:25 AM, Russell Peterson wrote:
The package I was adding had python scripts in it. The make process
for the package used the python distutils.core setup function. I
didn’t write the code… I’m just creating a recipe for it. This in
turn copies the scripts to various locations bu
On 02/09/2018 07:26 AM, Chang Rebecca Swee Fun wrote:
README | 2 +-
There is a typo in the commit message however :)
Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Settings mentioned in the README have been ported over and now users
are able to copy and start modifying for personal use cases.
This file will served as a reference to minimize errors when users
trying to create a new conf file by following the README.
Signed-off-by: Chang Rebecca Swee Fun
---
Signed-off-by: Chang Rebecca Swee Fun
---
README | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README b/README
index 84e140f..4a8181f 100644
--- a/README
+++ b/README
@@ -110,7 +110,7 @@ file:
--- snip ---
INHERIT =+ "buildhistory"
-BUILDHISTORY_C
Thanks, Alex. That was indeed the problem.
For those searching for answers to similar issues I will add what my particular
issue was.
The package I was adding had python scripts in it. The make process for the
package used the python distutils.core setup function. I didn’t write the
code… I
This particular one didn't provide a tarball.
Can't really say if it's an exception or tendency with the whl
starting to take over.
On Thu, Feb 8, 2018 at 3:04 PM, Giordon Stark wrote:
> This also works with the tarball URLs from pypi which is a bit easier to
> manage (version-wise).
>
> Giordon
This also works with the tarball URLs from pypi which is a bit easier to
manage (version-wise).
Giordon
On Wed, Feb 7, 2018 at 7:10 AM Alan Martinovic
wrote:
> Thanks, that worked!
>
> Steps:
>
> # On the build server
> devtool create-workspace
> devtool add https://github.com/jruere/multiproc
Hi,
thank you for the help. Here are some information about the configuration
Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi"
DISTRO
Greetings all,
I've created a board support package for the adzs-sc589-ezlite evaluation board
from Analog Devices. I would be very interested in hearing about how it can be
improved.
Take a look at it here:
https://github.com/spierepf/meta-adzs-sc589-ezlite
[https://avatars2.githubusercon
While building -trousers recipe, the below files are
not shipped but has been installed. The patch packages them
accordingly.
-- snip --
WARNING: lib32-trousers-0.3.14+gitAUTOINC+4b9a70d578-r0 do_package: QA Issue:
lib32-trousers: Files/directories were installed but not shipped in any package:
While building -trousers recipe, the below files are
not shipped but has been installed. The patch packages them
accordingly.
-- snip --
WARNING: lib32-trousers-0.3.14+gitAUTOINC+4b9a70d578-r0 do_package: QA Issue:
lib32-trousers: Files/directories were installed but not shipped in any package:
> On 7 Feb 2018, at 22:43, Máté Tüske wrote:
>
> Hi,
>
> I try to build custom image with mono. Previously I did it successfully, but
> now I ran into some issue and I cannot solve it.
> ERROR: mono-5.4.1.6-r0 do_package_qa: QA Issue:
> /usr/lib/mono/3.5-api/Microsoft.Build.Engine.dll contai
14 matches
Mail list logo
