On Tue, Nov 15, 2011 at 9:56 AM, Luca Fascione <lu...@wetafx.co.nz> wrote: > Also, note that if you have a header a.h inside zmq/ you can slightly > alter the CPPFLAGS and the files that say #include <a.h> still work > fine, whereas the opposite is quite a bit harder :-)
Hi, while moving the headers into their own sub-directories is nicer from packaging point of view I would be hesitant to implement this in stable releases. While this change is easy to implement for experienced C and C++ developers we do have large amount of user's that struggle compiling the guide examples. Applying this change would force them to use the -I flag / not being able to compile the examples in a way that they have used to. Also, this would potentially break large amount of builds that rely on the header being deployed to the default include path. You should be able to achieve the same result by packaging your local copy with: ./configure --prefix=/usr --includedir=/usr/include/zmq -- Mikko Koppanen _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
