> I should give you a heads up: we (the yocto project) are going to remove qt4
> builds from the autobuilder altogether, sometime during this cycle. The repo
> will stay, and patches will be accepted though.
Thanks for the heads up.
> So it's up to you to solve these issues, but I wouldn't want t
l even be possible to continue supporting qt4
going forward.
This may turn out like the openssl conflicts in that we'll need to
disable qt4's use of icu entirely.
On Wed, Jun 7, 2017 at 8:24 AM, Alexander Kanavin
wrote:
> On 06/07/2017 07:19 AM, Cody P Schafer wrote:
>>
>>
: ‘char16_t’ does not name a
type; did you mean ‘wchar_t’?
| typedef char16_t UChar;
| ^~~~
| wchar_t
May have to do with our use of `-std=gnu98++`.
Signed-off-by: Cody P Schafer
---
recipes-qt4/qt4/qt4-native.inc | 2 +-
1 file changed, 1 insertion(+), 1
r (occasionally) at populate_sdk time due to the lack of a
provider for the shared libraries.
Signed-off-by: Cody P Schafer
---
recipes-qt4/qt4/nativesdk-qt4-tools.inc | 4
1 file changed, 4 insertions(+)
diff --git a/recipes-qt4/qt4/nativesdk-qt4-tools.inc
b/recipes-qt4/qt4/nativesdk-qt4-
It looks like http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-dev/
is still sitting at 3.17.6, are their plans to merge the 3.18 changes?
Or does linux-yocto-dev wait on stable kernel releases?
Or is this blocked on something else I'm unaware of?
--
Cody
--
On Sun, Oct 19, 2014 at 4:10 AM, Khem Raj wrote:
>
[...]
> I have started to integrate clang into oe
> Which probably is quitquite similar to this effortwise. Its very
> prelimpreliminary. Check my github repo. I should add it to layer index
(repo link for the interested: https://github.com/kraj/
On Fri, Oct 17, 2014 at 1:48 PM, Martin Jansa wrote:
> On Fri, Oct 17, 2014 at 09:07:19AM +0100, Paul Barker wrote:
>> On 16 October 2014 18:46, Cody P Schafer wrote:
>> > Hi all,
>> >
>> > I'm working on creating a layer for the rust compiler (which u
Hi all,
I'm working on creating a layer for the rust compiler (which uses
llvm) and was wondering if there were any best practices and/or
examples people could point me at.
The compiler is designed to be built for multiple targets at once
(unlike the gcc model of having a single compiler build fo
This works with qt4 (non-embedded) when built natively, is there some
bitbake incantation I'm missing to have qt4e+cmake work? Or does qt4e
just not play nice with cmake?
Error message:
| [100%] Building CXX object CMakeFiles/kiosk-web.dir/kiosk.cc.o
|
/home/cody/obj/yocto/tmp/sysroots/x86_6
Depend on giflib-native, without this we end up pulling in the system's
one (which may be the wrong version)
Signed-off-by: Cody P Schafer
---
recipes-mono/libgdiplus/libgdiplus-native_2.10.8.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-mono/libgd
10 matches
Mail list logo
