On Aug 12, 2014, at 1:37 PM, Adam Strzelecki wrote:
>> On to my now standard question: Can you summarize the discussion so far into
>> a proposal on what you want to change? Keep it as short as possible :) For
>> example, I think it’s understood that (incremental) framework coping is fast
>>
On 2014-08-12, at 07:15 PM, Adam Strzelecki wrote:
>> Err, what? Standard use case is @rpath + copy frameworks. So if that's done
>> by default, and macdeployqt is deleted, no one is bothered.
>
> But app won't start, because it needs to resolve Qt libs referenced via
> @rpath to @executable_p
> Err, what? Standard use case is @rpath + copy frameworks. So if that's done
> by default, and macdeployqt is deleted, no one is bothered.
But app won't start, because it needs to resolve Qt libs referenced via @rpath
to @executable_path/../Frameworks, thus accompanying `QMAKE_RPATHDIR =
@exec
On 2014-08-12, at 06:50 PM, Adam Strzelecki wrote:
>> Please stop saying that to fuel your argument just because I disagree with
>> some of your points; it sounds kind of rude. Also, I am one of these
>> "stakeholders", though I'm not sure what definition you're going off of,
>> because the di
> Please stop saying that to fuel your argument just because I disagree with
> some of your points; it sounds kind of rude. Also, I am one of these
> "stakeholders", though I'm not sure what definition you're going off of,
> because the dictionary's definition "a person with an interest or conce
On 2014-08-12, at 12:36 PM, Adam Strzelecki wrote:
>> Default behavior: I’m on favor of keeping it opt-in, either via "CONFIG +=
>> bundle_frameworks" or “make bundle”
>
> Me too. However as I said previously stakeholders are to decide. I don't want
> start over this discussion with Jake.
Ple
> The target name: Should that be “deploy”? “make deploy" would then perform
> platform-specific deployment.
Well, I think "deploy" isn't a correct name. IMHO deployment is more like
uploading application (service) to target system. We aren't to upload or
transfer anything.
So either "bundle"
On Monday 11 August 2014 19:33:37 Jake Petroules wrote:
> Neither - v4.8.6 dmg from qt-project.org.
The old scripts specified -prefix /usr/local/Qt- and then did manual
copying
of the frameworks to system dirs.
I don't think we're going to change Qt 4's way of doing things anymore.
--
Thia
> On 12 Aug 2014, at 16:25, Adam Strzelecki wrote:
>
> Okay, Phase II.
>
> (1) Introduce "bundle_frameworks" CONFIG option, and set it default for
> "rpath" shared builds on iOS & OS X
>
> (2) Introduce "bundle" make target, when "bundle_frameworks" CONFIG is set,
> it is added to "all"
>
>
Okay, Phase II.
(1) Introduce "bundle_frameworks" CONFIG option, and set it default for "rpath"
shared builds on iOS & OS X
(2) Introduce "bundle" make target, when "bundle_frameworks" CONFIG is set, it
is added to "all"
(3) Make's "bundle" will copy (update if not there) all used Qt framework
Hi,
I am using Combobox component of qt quick controls, i am facing a
strange issue.
I am calling the slot onPressedChanged, inside that model gets updated.
If the item count is less than 3 then the combo dropdown is showing
black dropdown. The items are visible only when the mouse hover is do
> On 12 Aug 2014, at 13:37, Adam Strzelecki wrote:
>
>> On to my now standard question: Can you summarize the discussion so far into
>> a proposal on what you want to change? Keep it as short as possible :) For
>> example, I think it’s understood that (incremental) framework coping is fast
>>
> On to my now standard question: Can you summarize the discussion so far into
> a proposal on what you want to change? Keep it as short as possible :) For
> example, I think it’s understood that (incremental) framework coping is fast
> - no need to go into details. On the other hand I think it’
> On 11 Aug 2014, at 23:15, Jake Petroules wrote:
>
> This was mostly a counterargument to people complaining against copying
> frameworks into the bundle. However, copying frameworks into the bundle is
> the correct solution, and is what must be done in the end.
>
> It'll be nice when qbs so
Hi all,
We are planning to release Qt5.3.2 pretty soon, at the end of August or early
September.
There is new snapshot available for Qt5.3.2:
Windows: http://download.qt-project.org/snapshots/qt/5.3/5.3.2/2014-08-12_133/
Mac: http://download.qt-project.org/snapshots/qt/5.3/5.3.2/2014-08-12_103/
On Aug 11, 2014, at 11:15 PM, Jake Petroules
wrote:
> On 2014-08-11, at 10:42 AM, Ziller Eike wrote:
>
> In a terminal session, simply:
>
> $ export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:/path/to/Qt/Frameworks
> $ open /apps/MyApp.app
>
> In Creator, just click
Hi!
Is there a Windows WMF wizard here, who could have a look at the
following bug:
https://bugreports.qt-project.org/browse/QTBUG-32481
If was opened over a year ago and seems to be still valid on Qt 5.3.1.
This bug makes is very difficult to have long-running multimedia
applications. It would
17 matches
Mail list logo
