Hmm.. thats interesting.
So, does that imply that aqua provides a X11-like API (w/ libs) or
does that mean that the actual people writing packages (like
openoffice) need to support aqua calls conditionally compiled in on
detection of the aqua include/libs?
thanks
On Jan 24, 2009, at 1:25 PM, Harry van der Wolf wrote:
It is something completely different. Most linux, netbsd and freebsd
packages rely on X11. MacOSX has support for x11 but the native
windowing system of MacOSX is aqua. Using the -x11 option means that
you don't build for X11. An increasing amount of binaries and
libraries support native aqua and in that case I don't want to build
for X11. It's slower, bigger (X11 takes also memory and resources
next to the already available aqua) and ugglier. But the last is off
course a matter of taste.
Note that some binaries and libraries are still considered beta
under aqua (like Gimp) but function very good.
If you take a look at openoffice (not macports) you see what I mean.
It has already been available for MacOSX in X11 form for a long
period.
Recently they also released a 3.0 beta version for Aqua which works
fine.
NeoOffice is an aqua spin-off of OpenOffice and has a native Aqua
interface for about 1½ years now. In versioning it runs a bit behind
OpenOffice (OOO 3.0.x versus NOO 2.2.5)
Note also that some packages that are compiled with -x11, simply
miss the X11 gui but only compile/create the command line versions.
Harry
2009/1/24 Timothy Lee <tim...@rochester.rr.com>
Harry-
You made reference to adding the -x11 tag to your variants.conf.
By doing this, do you force macports to use Apple's X11? Or is it
something else entirely different?
thanks
On Jan 24, 2009, at 12:59 PM, Harry van der Wolf wrote:
2009/1/24 Timothy Lee <tim...@rochester.rr.com>
Thanks for the reply Harry-
I'm fairly sure that I will need to lipo together the builds for
Musicbrainz' Picard.
So - in your experience what are all the options that I must set
after a fresh src install to have a 10.5 setup building binaries
for 10.4?
Nothing more than setting the right options in your macports.conf
and then see how far you get.
2009/1/24 Timothy Lee <tim...@rochester.rr.com>
On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote:
On Jan 23, 2009, at 09:11, <tim...@rochester.rr.com> <tim...@rochester.rr.com
> wrote:
Joshua Root <j...@macports.org> wrote:
Timothy Lee wrote:
Do you know if its possible for me (on leopard) to build x86 code
(all
my macports ports) that will also run on Tiger?
Short of physical access to an intel 10.4 install, is there
anything I
can do?
Don't forget to use Reply All so the discussion goes to the list as
well. There are no guarantees that this will work, but the way to do
what you want would be to set universal_target to 10.4,
universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and
universal_archs to i386. Then build everything with +universal
(best to
add it to your variants.conf).
Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11
does not exist on Tiger.
If I do this, how will I be able to run the executables on my 10.5
setup?
I ran into the same issue and simply decided to make links.
On Tiger I simply did "sudo ln -s /usr/X11R6 /usr/X11". If you
build on Tiger and bring them to Leopard you do
"sudo ln -s /usr/X11 /usr/X11R6".
This works only on your own system off course, unless you make an
installer that checks whether it runs on Tiger or Leopard and
creates a softlink accordingly.
Harry
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
