On Sun, Dec 7, 2014 at 10:29 PM, Alejandro Exojo wrote:
> El Sunday 07 December 2014, Luciano Montanaro escribió:
>> On Sun, Dec 7, 2014 at 10:33 AM, Alejandro Exojo wrote:
>> > That's the opposite of what most people are trying to do.
>> >
>> > If the overhead is negligible, you may not care muc
El Sunday 07 December 2014, Luciano Montanaro escribió:
> On Sun, Dec 7, 2014 at 10:33 AM, Alejandro Exojo wrote:
> > That's the opposite of what most people are trying to do.
> >
> > If the overhead is negligible, you may not care much of shipping all the
> > assets in one binary package, of whi
On 12/7/2014 11:33 AM, Alejandro Exojo wrote:
However, the main thing that motivated me to dig into the issue and
send the mail was libsailfishapp. That library is, AFAIK, only
relevant on Sailfish, and also requires one to add special code in
main(). That can't be done at
There, you said i
On Sun, Dec 7, 2014 at 10:33 AM, Alejandro Exojo wrote:
> That's the opposite of what most people are trying to do.
>
> If the overhead is negligible, you may not care much of shipping all the
> assets in one binary package, of which the user will only see a part, but
> other applications might p
El Saturday 06 December 2014, Lorn Potter escribió:
> Tizen also and their own branch even.
>
> There are also quite a few other devices that have their own mkspec, so
> there is precedence for supporting a sailfish/jolla platform mkspec.
Oh, true, I forgot them.
> (...)
> Well, this one is e
El Saturday 06 December 2014, Luciano Montanaro escribió:
> Actually, no, you want to detect features at runtime, not at build time.
That's the opposite of what most people are trying to do.
If the overhead is negligible, you may not care much of shipping all the
assets in one binary package, of
