[KDE/Mac] QStandardPaths possible solution

[Jeremy Whiting]

Oops, seems I forgot to try removing some of those #includes, I'll do that
once Qt finishes building to clean it up a bit. Comments on the code itself
and approach are welcome though.

On Mon, Jan 5, 2015 at 1:51 PM, Jeremy Whiting <jpwhiting at kde.org> wrote:

> Ok, we've had plenty of discussion on the other thread(s) imo and should
> start looking at a real solution. I see the following requirements, but
> please correct me if I'm wrong.
>
> 1. It should allow adding new paths via environment variables, and
> probably have a default <-- fixes CI issues on mac and also possibly
> runtime issues.
> 2. It should be fixed in Qt itself. Since Feature Freeze for Qt 5.5 is
> coming up in feb this needs to start now if we hope to get the fix into 5.5
> (I, for one would like this)
>
> I've looked at Marko's patch and had to tweak it a bit to get it to apply
> to qt 5.4 branch. I've attached a first try here while it builds at the
> same time so I can test it.
>
> I thought I'd also mention some long term goals/use cases for us to keep
> in mind.
>
> 1. We want developers on mac to help with kde issues on mac, so getting to
> the point of (install standard qt, build with kdesrc-build or manually
> against it, run, profit) is a big goal for me.
> 2. We also want kf5 frameworks to be usable in other applications, so
> having the ability to say yes, use KNewStuff3 (which stores data in a
> standard place to know what it has installed, etc.) in your application on
> osx is just fine and will work with any Qt >= 5.5
> 3. We want (maybe?) our applications to be downloadable dmg files that can
> simply be copied into /Applications and run.
>
> Actually for 3 I have some questions. On OS X do applications typically
> bundle everything inside their .app or do some install for example a shared
> copy of Qt or other libraries? I've seen mention of VirtualBox and other
> applications on the other thread. Do they all put Qt inside their .app
> folder? Do we want to do the same for kde applications to be installable
> standalone, like Kate, Kanagram, Kgeography, KTuberling, KPat, etc.
>
> 4. We want macports to be able to easily create ports of our applications
> and libraries. This seems like it will be provided easily if 1 is
> accomplished, but may need to be kept in mind as there are some minor
> differences.
>
> So if this patch looks ok to those reading this list I'll push it to
> gerrit and get the review process started. If there are things we should
> fix first, let me know and I'll adapt as needed.
>
> BR,
> Jeremy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-mac/attachments/20150105/3fa3b071/attachment.html>