Uhm, this one might be hard to debug for me, as Control seems to be not mapped to Command in ViirtualBox...
As you know there are two modifier keys on Mac OS X. One is Command which corresponds to Ctrl in Windows or Linux. The other one is Control which corresponds to Meta or Windows key. There is no problem with Command, it works as Ctrl in shortcuts. But when you set something to Meta, Control key on Mac doesn't do anything.
Alright then, I am going to make packages despite the icon problems if you don't have any objections
I have encountered same problem as you, but I think it's more about Finder cache and probably Qt applications in general, not specifically Otter. Because after first launch custom icon shows normal every time. Also if problem is about some .plist error, custom icon should never be visible.
There is other problems specific to Mac OS X. One of the big ones is when you cycle through tabs with keyboard shortcut tab list doesn't show, but when you do this with mouse gestures you can see the tab list. Also you can't use Meta (Control) key in custom keyboard shortcuts. You can set it, but it doesn't work. IDK if there is something you can do about it.
Also other question is should I include QtWebEngine? Seems like you don't include QtWebEngine packages for a couple of weeks. Is there some problem?
Sorry about the delay. I have been busy for some time. But good news is I have finally managed to build Otter with CMake and packaged with macdeployqt. Everything seems fine now, but I am not sure that using macdeployqt instead of CPack would make any difference. Also I have compiled Qt 5.5 RC with -openssl-linked option so that weekly 77 and 78 are using the latest OpenSSL 1.0.2c not the outdated one inside the Mac OS X.
Also I recently noticed that with 5.5 release Qt can be able to use Mac OS X native backend instead of OpenSSL. I am thinking about building Qt with this configuration. Thinking that it will become the default option in 5.6 this would be a smart decision, isn’t it?
For Mac OS X 10.7 Lion users I am thinking about building Qt 5.4.2 with updated OpenSSL libraries. I know 5.4.2 is outdated, but I suppose with 5.5 support for 10.7 is dropped. So an outdated package is better than no package
@Fotmat C I am glad to see someone except me is using these Mac packages Weekly 77 and 78 should resolve your issues with SSL. Let me know if it works. BTW which Mac OS X are you using?
I'm using SDK. Is building myself more preferable?
Now I have installed CMake using Homebrew and I will experiment with it. But I have a question: How am I going to use that script? I have no programming experience so I don't know what to do and I need assistance Am I going to paste that script into a text file and name it CPackConfig.cmake?
Okay now I posted the Dropbox folder link to the unoffical packages page.
It sure appears doable but it looks a lot more complicated than macdeployqt. But from now on I am going to investigate a way to make Mac application bundles with CMake and CPack. I hope I can succeed
Also I have couple of Mac specific issues with Otter. Is this the place for talking them or should I fill bug report on GitHub or SourceForge?
How can I put links to this page? Should I send you the links?
I am using Qt Creator and its packaging tool macdeployqt for making distributable application packages. I know that you prefer CMake and this was my first choice but I couldn't find an easy way to make packages with CPack. It is complicated and problematic with Mac applications. At least not easy as macdeployqt :-)
Is using Qt Creator instead of CMake okay for distributable packages? Should I look for ways to use CMake and CPack?
First of all I must say I'am very impressed with this project. Finally there is a browser to fill the gap that old Opera has left. Thanks for everyone who makes this project happen.
Second I see that there is no Mac specific packages right now, you must compile from source code to use it and that is a big disadvantage for most of the users. So I decided to contribute to comminity and make Mac OS X packages for fellow Mac users and of course myself
Now my question is who should I send them and how? I have packages from Beta 5 to Beta 6 and I have uploaded all of them to Dropbox. I'am waiting for guidance
