Build for mac os without significant changes #150
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "feature/osx-build"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Build for mac os without significant changes of master's code (insead of osx branch). A bit later I can provide signed binary build for osx.
Very well. I tested it both under Linux and OSX and everything works like a charm. Thank you.
We should also try to understand how to include the konsole plugin into the app directory.
Sorry, what do you mean? Do you mean move sources from konsole-qml-plugin
to app or something with .app on OSX? And what goal do you suppose?
2014-10-10 0:22 GMT+04:00 Filippo Scognamiglio notifications@github.com:
С уважением, Тохин Симаков.
Yeah, that was a very short comment. Right now the application compiled
under OSX doesn't work without manually installing the konsole plugin. I
think the konsole library (the dlsym file plus the assets) should be moved
in the .app directory (cool-retro-term.app) where the executable can locate
it.
2014-10-09 22:29 GMT+02:00 Anton Simakov notifications@github.com:
Ok, I'll think about it
пятница, 10 октября 2014 г. пользователь Filippo Scognamiglio написал:
С уважением, Тохин Симаков.
Right now after build we have cool-retro-term.app. User could move it to
Applications folder and use. But installed qt5 required (I installed qt5
view brew "brew install qt5")
I did nothing special with konsole plugin and it works as is.
2014-10-10 0:34 GMT+04:00 Filippo Scognamiglio notifications@github.com:
I need more explanations about the issue to make it visible and clean.
Let's start saying that I'm definitely not an expert in terms of OSX. From what I understand the app bundle has to contain all the libraries needed by the application. In our case we need only the qt5 libraries and the konsole-plugin. The qt5 libraries can be bundled using tools like macdeployqt (just macdeployqt cool-retro-term.app should be enough) which are smart enough to include only the pieces of the framework we actually use.
For the konsole plugin the matter is a little bit more complex. Qt looks in a series of folders to get the qmlplugins (that's why in main.cpp I'm adding the custom "import" folder where our plugin is located under linux) and effectively run the application. On OSX I can't directly run the application (open cool-retro-term.app) because it lacks the konsole-plugin. The only solution to these problems are:
If you are able do run the application without issues it means that you are in one of the two solutions. In other words where does your app locate the c++ plugin?
Hi. I figured out how to build stand alone cool-retro-term for mac. I
created pull request https://github.com/MaximAlien/macdeployqt/pull/1 to
macdeployqt application with small fix and after that we can use it for
deployment
cp -r imports cool-retro-term.app/Contents/MacOS/
2014-10-10 15:32 GMT+04:00 Filippo Scognamiglio notifications@github.com:
С уважением, Тохин Симаков.
Thank you very much. With your commands I have been able to create a
standalone app bundle. I had to add the line: "import
QtQuick.PrivateWidgets 1.0" to InsertNameDialog.qml because macqtdeploy
missed those imports. I think we can start distributing the dmg file. Just
a quick information, when you launch the app (not from command line) does
it login automatically (or you read something like "bash3.2:")?
2014-10-13 8:31 GMT+02:00 Anton Simakov notifications@github.com:
2014-10-13 16:26 GMT+04:00 Filippo Scognamiglio notifications@github.com:
Latest macqtdeploy puts PrivateWidgets to app bundle.
cool-retro-term.app/Contents/MacOS/QtQuick/PrivateWidgets/
libwidgetsplugin.dylib
Yes. When I open cool-retro-term I am logged in but ~/.bash_profile is not
applyed
С уважением, Тохин Симаков.