2009/1/26 Vincent Lefevre <[email protected]> > On 2009-01-24 19:25:51 +0100, 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. > > But in MacPorts, is it possible to have both an Aqua version and an > X11 version (for execution on a remote display)? >
No. That's not possible in one macports tree. Libraries and binaries need to be compiled either for X11 or for Aqua. If you are adventurous you can off course create/install the default tree in /opt/local and compile macports by hand and set the prefix and so on to (for example) /aqua/local. It will be a complicated setup as you also have to be very careful about PATH settings and so on, but I have used it a short while when moving from X11 to Aqua for avidemux (but it is very error prone). Harry
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
