Issue 111496 - [meta] allow building with internal python on Mac OS X
Summary: [meta] allow building with internal python on Mac OS X
Status: CONFIRMED
Alias: None
Product: porting
Classification: Code
Component: MacOSX (show other issues)
Version: DEV300m77
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on: 111498 111500 111497
Blocks:
  Show dependency tree
 
Reported: 2010-05-09 21:09 UTC by lohmaier
Modified: 2023-05-21 16:47 UTC (History)
3 users (show)

See Also:
Issue Type: PATCH
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
combined patch of the individual issues for convenience (25.04 KB, patch)
2010-05-19 13:26 UTC, lohmaier 		no flags Details | Diff
modified against m86 (17.03 KB, text/plain)
2010-08-30 19:18 UTC, florian 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description lohmaier 2010-05-09 21:09:08 UTC 
Got hacky patch to that makes it work on Mac, but affects other platforms, 
especially python/prj/d.lst

This is a meta-issue tracking open questions on how to solve these (code/style) 
conflicts.
Comment 1 lohmaier 2010-05-10 00:07:29 UTC 
Patches to create a working build with OOo internal python attached to the 
depending issues.

Both running macros from within OOo as well as using the shipped python to 
control OOo from the outside works.

ToDo:
* decide what to do with the ugly d.lst
* python scripts in bin directory within framework reference build (python's 
installation destination) directory in shebang (remove or change?)
* adapt scp2 patch to not hardcode version, but use define for major.minor
* make name of the framework a variable (well, only necessary if Oracle cannot 
live with OOoPython.framework in their tree :-)) - by configure/set_soenv or in 
solenv?
Comment 2 lohmaier 2010-05-10 01:09:53 UTC 
forgot to mention the most important ToDo: need to run install_name_tool to 
relocate the framework.
Comment 3 eric.bachard 2010-05-10 05:32:47 UTC 
Removing me.
Comment 4 lohmaier 2010-05-10 18:53:49 UTC 
d.list has been shrinked down considerably. As I moved the creation of the zip to 
python directly, there's no need to copying the whole thing to solver. Header and 
the actual framework binary is enough. (the d.list entries for the other OS still 
copy lots of files in addition though)

Also the install_name_tool usage has been added to the patches as well. Now 
python keeps working, even if you dare to erase your build tree :-))
Comment 5 lohmaier 2010-05-19 13:15:59 UTC 
Done from my side.

ToDo:
* decide whether OOo-internal python should be default for Mac in future

Maybe: Make the framework-name (currently OOoPython.framework) a variable.

and of course: Give it a spin on various versions of Mac OSX
Comment 6 lohmaier 2010-05-19 13:26:05 UTC 
Created attachment 69534 [details]
combined patch of the individual issues for convenience
Comment 7 florian 2010-08-30 19:18:29 UTC 
Created attachment 71485 [details]
modified against m86
Comment 8 florian 2010-08-30 19:22:18 UTC 
Patches work for me, macros still work :) and import uno also works with the internal python.
Though I am not really happy about the added disk space usage (ca. 75MB-80MB for the framework)...
Comment 9 oooforum (fr) 2023-04-27 06:34:37 UTC 
Set type from "task" to "patch"

Does any developer know if this patch can be pushed into AOO 4.x?
this would be very useful as python 2.7 is no longer provided under MacOS.