1 |
> On 21-01-2011 22:01:17 +1300, François Bissey wrote: |
2 |
> > I have been toying with a Gentoo prefix on OS X (10.5) for the |
3 |
> > last month. |
4 |
> > |
5 |
> > I spent most of my time getting things in shape to have sage from |
6 |
> > the sage-on-gentoo overlay build on OS X. |
7 |
> > |
8 |
> > I have something that runs now and I'd like to clean up my work |
9 |
> > and put some of it in good shape for submission. |
10 |
> > |
11 |
> > I was working on x86-macos with 10.5 and a friend of mine was |
12 |
> > testing on x64-macos with 10.6 (he also have a ppc-macos, presumably |
13 |
> > 10.4 on which he plans to test the stuff). |
14 |
> > |
15 |
> > 1) I have one ebuild in which I need to set |
16 |
> > MACOSX_DEPLOYMENT_TARGET |
17 |
> > How do I identify the various flavours of OS X, 10.4, 10.5, 10.6, to set |
18 |
> > it right? |
19 |
> |
20 |
> I'd like to trace down why your package needs this to be set. The |
21 |
> Prefix profiles for OSX already set MACOSX_DEPLOYMENT_TARGET explicitly |
22 |
> to the right version. Check make.defaults and profile.bashrc. |
23 |
> |
24 |
|
25 |
I didn't know this at the time I wrote my message. It is indeed set just fine |
26 |
by the system. |
27 |
|
28 |
> > 2) framework: I noticed that we build the python framework. Do we |
29 |
> > preferably build framework? Or the reverse? I have worked on dev-lang/R |
30 |
> > and I didn't build it as a framework and ended up with a bunch of .so |
31 |
> > which should have been ".bundle" I believe. |
32 |
> |
33 |
> We build the framework *next* to the normal UNIX way, just because of |
34 |
> graphical application support for Python. Due to how OSX works, a |
35 |
> graphical application that uses CoreGraphics (or something) needs to |
36 |
> call those methods from a Bundle environment, which a Framework is. |
37 |
> It is preferred not to build in frameworks in Gentoo Prefix from my |
38 |
> point of view where possible. Note that Python is built in both ways, |
39 |
> such that you only need to worry about the Framework when you do a |
40 |
> graphical app (which in general only looks for the Framework, so that |
41 |
> works out nicely). |
42 |
> |
43 |
> The .so vs .bundle is an a problem sometimes solved using elibtoolize, |
44 |
> but in R's case probably by patching the buildsystem. |
45 |
> |
46 |
|
47 |
Ok, I tried to build the framework for R but the install routine to install |
48 |
the framework is just awful. |
49 |
|
50 |
Francois |
51 |
|
52 |
This email may be confidential and subject to legal privilege, it may |
53 |
not reflect the views of the University of Canterbury, and it is not |
54 |
guaranteed to be virus free. If you are not an intended recipient, |
55 |
please notify the sender immediately and erase all copies of the message |
56 |
and any attachments. |
57 |
|
58 |
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more |
59 |
information. |