Hi all,
I was wondering how the mer build engine builds things for armv7hl. When
I login, I only found a i486 gcc, none for arm.
Is there any documentation how it builds a QT project for armv7hl, that
is the actual commands used when one clicks the build icon in qtcreator
(with a vanilla
for all project, click the project tab and add a kit, that all. Than select
target from the build button (bottom left)
to be able to deploy you have to add a device from tool-options-mobile ;
dev mod must be enable (may need to reboot the phone) ; you can use the
wifi ip, no need to plug a cable.
if you have spec for your project you can compile it using mb2 -t
SailfishOS-armv7hl build command.
10.01.2015 16:13, Dirk Zimmermann пишет:
On 10.01.2015 11:15, jerome levreau wrote:
for all project, click the project tab and add a kit, that all. Than select
target from the build button
Just reporting some issues I had when trying to update the SDK.
I've updated the SDK to 3 computers, on two I got this when the
maintenance tool was updated+restarted:
Your installation seems to be corrupted. Please consider re-installing
from scratch.
And when doing the update plenty of:
Error
On 10/01/15 11:13, Dirk Zimmermann wrote:
On 10.01.2015 11:15, jerome levreau wrote:
for all project, click the project tab and add a kit, that all. Than select
target from the build button (bottom left)
to be able to deploy you have to add a device from tool-options-mobile ;
dev mod must be
I had this too.
Did a complete re-install and no issues so far.
// Pete
Kaj-Michael Lang kirjoitti la tammikuuta 10 15:57:21 2015 GMT+0200:
Just reporting some issues I had when trying to update the SDK.
I've updated the SDK to 3 computers, on two I got this when the
maintenance tool was
On 10.01.2015 11:15, jerome levreau wrote:
for all project, click the project tab and add a kit, that all. Than select
target from the build button (bottom left)
to be able to deploy you have to add a device from tool-options-mobile ;
dev mod must be enable (may need to reboot the phone) ; you
On 10.01.2015 14:30, David Greaves wrote:
Typically you'll approach this by getting into the sb2 environment (like
a chroot) and running ./configure; make
To do it more cleanly and in a manner that could eventually become part
of the OS (ie in mer-tools) you'd create a simple rpm package and
