Feature #418: === Configuration & Build ===
Revise deployment instruction for Mac
|Status:||Archived||Start date:||28 Oct 2014|
|Target version:||Sprint 25|
Out current deployment instruction Deployment_for_Mac_Os_X assume build of BornAgain using macport libraries.
As a result of dmg generation we get BornAgain package which contains all dependencies on board, including macport's version of Python.
This approach is Ok, when BornAgain will be used via graphical user interface. But if user will use libBornAgainCore library from our installation with system version of Python, this approach might lead to the problems due to inconsistency between macport's boost+python and system python libraries.
btw, we have similar issue #787.
When user compiles BornAgain from scratch using macport, and then trying to use libBornAgain core library in PyCharm (which uses by default system Python) then there is segmentation fault in boost+python machinery.
Consider following change in deployment procedure for mac.
- boost libraries should not be installed via macport (since it will bring also macport's Python), but compiled from the scratch using system Python
- fftw3, gsl might be installed via macport
- BornAgain should be compiled using system Python from /usr/bin
- This build has to be used for dmg package generation
Find better place for thisbornagain.sh inside dmg archive