Hi! > 1) Does the ports tree magically tweak CFLAGS or whatever when you build a > port, to include things like /usr/local/include and /usr/local/lib?
Yes. If you run a port-build and log the build, you'll see many calls like this: libtool: compile: cc -DHAVE_CONFIG_H -I. -I../../config -D_REENTRANT -DUSE_IOPERM -DIPV6 -isystem /usr/local/include -O2 -pipe -D_WANT_SEMUN -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -MT libmiscutil_la-fd.lo -MD -MP -MF .deps/libmiscutil_la-fd.Tpo -c fd.c -o libmiscutil_la-fd.o >/dev/null 2>&1 and here you see the -isystem /usr/local/include... > I don’t see anything that would do this in /usr/ports/Mk USES= localbase triggers those. See Mk/Uses/localbase.mk > 2) Is there a standard method for ports that need to run autogen? Somewhat for GNU autoconf: see Mk/Uses/autoreconf.mk -- p...@freebsd.org +49 171 3101372 Now what ?
