Would that be better than just adding a hierarchy layer under the src/include directory? So, instead of symlinking freeradius-devel to include during the make process, you just have src/include/freeradius/. Then your include line looks like: #include <freeradius/includefile.h> and your CFLAGS line looks like: CFLAGS += -I$(top_builddir)/src/include I think this would be more along the lines of what other projects do and possibly a little less confusing. --Mike ----------------------------------- Michael Griego Wireless LAN Project Manager The University of Texas at Dallas Alan DeKok wrote:
I think I'm going to fix the CVS head:
src/Makefile ln -s include freeradius-devel
src/main/Makefile src/lib/Makefile src/lib/rules.mak CFLAGS += -I$(top_builddir)/src
And then change all of the
#include "libradius.h"
to
#include <freeradius-devel/libradius.h>
Which will fix the retarded Solaris issues once and for all.
After we clean up the other header files, we can use <freeradius/file.h> for include files everyone should use, and <freeradius-devel/file.h> for include files that exist only in the current build tree.
Comments?
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html