My platform is OSX with clang and libc++.
I was looking at your makefiles to see what it would take to get them to work on OSX. I notice the following needs...
1) enhance your build system so that I can specify the locations of my copies of your dependencies (headers and libs).
2) do not just use the '-l' option to specify libraries. We use static libraries heavily and '-l<libname>' will default to the dylibs (shared libraries) instead of the static libs.
3) allow specification of the platform SDK (-isysroot) in the compiler and linker flags.
NOTE: if instead of using raw make files you use the autoconf system, then all of this will be done for you as autoconf is flexible enough to allow one to specify his own custom linker flags, compiler flags, installation prefixes, compiler versions, and dependency locations.
I was looking at your makefiles to see what it would take to get them to work on OSX. I notice the following needs...
1) enhance your build system so that I can specify the locations of my copies of your dependencies (headers and libs).
2) do not just use the '-l' option to specify libraries. We use static libraries heavily and '-l<libname>' will default to the dylibs (shared libraries) instead of the static libs.
3) allow specification of the platform SDK (-isysroot) in the compiler and linker flags.
NOTE: if instead of using raw make files you use the autoconf system, then all of this will be done for you as autoconf is flexible enough to allow one to specify his own custom linker flags, compiler flags, installation prefixes, compiler versions, and dependency locations.