configure.cflags-append "-I/usr/X11R6/include"

configure.cppflags-append "-I/usr/X11R6/include"

configure.ldflags-append "-L/usr/X11R6/lib"

with this?

configure.pkg_config_path ${prefix}/lib/pkgconfig:${x11prefix}/lib/pkgconfig

the pkg_config_path solved some problems for me when I moved from Tiger to Leopard, but when I try to replace cflags, cppflags and ldflags with it, the configure fails.

On Fri, Mar 28, 2008 at 11:34 AM, Anders F Björklund <afb@macports.org> wrote:

Rainer Müller wrote:

>> The first version is better (lib:), because then one can use
>> a system version of X11 (such as Apple's X11.app) instead of
>> having to install either of the "XFree86" or "xorg*" ports...
>
> But the XFree86 port also checks for X11 and the X11SDK and spits
> out error messages explaining what the user needs to install.

As long as the library (i.e. libX11.dylib) is present, it doesn't
really matter what the port part of the depends requirement says...

It just says "XFree86" out of old habit, there's no need to update
it to say "xorg" if the recommendation is to use system X11 anyway ?

>> Currently GCC and X11 are on the list of exceptions where
>> using the system versions is generally recommended over
>> building a new version from ports (unless somehow needed)
>
> X11 in MacPorts is totally outdated, I think. Someone could step up
> to convert to Xquartz?

I don't think X11 in MacPorts (XFree86/xorg) is used anymore,
but it could be nice to have a new Xquartz-based port anyway:
http://trac.macosforge.org/projects/xquartz/wiki/DeveloperInfo

But most users would probably use the offical binaries, though.
The ports (XFree86/Xorg/Xquartz) would be if you wanted to
compile from source code, or otherwise utilize Open Source.

--anders

_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users