Em qua 26 fev 2014, às 13:41:23, Filip Piechocki escreveu:
> Okay... seems that I found te cause - there are no fonts installed on my
> system. How to force Qt to install qtbase/lib/fonts somewhere?
If you're using the system fontconfig library, shouldn't you install the fonts
in the systemwide l
2014-02-26 13:41 GMT+01:00 Filip Piechocki :
> Okay... seems that I found te cause - there are no fonts installed on my
> system. How to force Qt to install qtbase/lib/fonts somewhere?
>
Hi,
check if the following packages are installed on your target system:
qtbase-fonts-qpf
qtbase-fonts-ttf-de
Okay... seems that I found te cause - there are no fonts installed on my
system. How to force Qt to install qtbase/lib/fonts somewhere?
Best Regards,
Filip Piechocki
On Wed, Feb 26, 2014 at 11:55 AM, Filip Piechocki wrote:
> I am using Poky from dora branch.
> I've updated freetype and fontconf
I am using Poky from dora branch.
I've updated freetype and fontconfig to the latest versions (freetype
2.5.2, fontconfig 2.11.0) from poky master but still no success :( which is
weird as I used poky master some time ago and it was working (but it is
hard to use master branch as it is not building
On 23 Feb 2014, at 9:37 PM, Thiago Macieira wrote:
> Em dom 23 fev 2014, às 20:44:16, Filip Piechocki escreveu:
>> For me it looks good, maybe there is something wrong with fontconfig or
>> freetype?
>
> That's my guess, yes.
FWIW I saw this problem too when experimenting with Qt on Wayland on
Em dom 23 fev 2014, às 20:44:16, Filip Piechocki escreveu:
> For me it looks good, maybe there is something wrong with fontconfig or
> freetype?
That's my guess, yes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
_
My config.summary looks like this:
Configure summary
Building on: linux-g++ (x86_64, CPU features: mmx sse sse2)
Building for: devices/linux-rasp-pi-g++ (arm, CPU features:)
Platform notes:
- Also available for Linux: linux-kcc linux-icc linux-cxx
qmake vars .. styles
Em dom 23 fev 2014, às 09:13:55, Filip Piechocki escreveu:
> Any idea whats causing this problem?
Check your config.summary in the build and see if there are "no" items where
you should have yes. As a general rule, you want to have "yes" everywhere,
except where you know for sure that you don't
