[GCompris-devel] MacOSX deployment

[JAZEIX Johnny]

Hi,

the BUILD_STANDALONE variable should be set to ON by default for macOS 
(this variable is set to copy all the Qt/Qml plugins inside the 
package). I'm not sure if it works the same on macOS as for windows 
package, but on windows, running the "make package" copies the dynamic 
libraries besides the GCompris executable.
Could you list us the content of the package to see if there are missing 
files? And if you have some time, check if there are more/less files in 
the 0.18 and run the "otool -L" also on it?

Thanks,

Johnny

On 01/16/15 22:42, B.J. wrote:
> 	Now that 0.26 compiles & runs on the local machine, it breaks when the app package is copied to other machines (the one created at the end via “make package”).  According to otool -L gcompris-qt (which seems to work like the ldd in linux) they’re all linked to /Users/username/Qt/5.4/clang_64/lib/Qt****.framework …
>
> 	In order to localize this in the mac’s .app structure as it’s supposed to, I wrote a shell script that re-linked them to the proper place using install_name_tool, but then I got weird thread-related crashes.  I’m probably not using cmake correctly to make a standalone target, since this project was deployed as a stand-alone package in version 0.18.  I saw the -DBUILD_STANDALONE=ON option in the project’s CMakeLists.txt file but it doesn’t seem to change the way the package is generated…am I missing something or should I keep trying it the long way?  Have a great weekend all :)
>
> 	B.J.
> _______________________________________________
> GCompris-devel mailing list
> GCompris-devel at kde.org
> https://mail.kde.org/mailman/listinfo/gcompris-devel