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
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 (bott
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 e
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)
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.
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 sailfish
