On 8/4/19 4:17 PM, Alessio Vanni wrote: > A similar issue is that if I use autoconf I can't include my own > config.h file, as many entries there are overridden by gnunet_config.h. > In particular, macros like PACKAGE are defined with the GNUnet's value > rather than mine. If I include config.h after gnunet/platform.h, I get > a number of warnings about redefining already defined values.
Yes, if you have your own build system, you should not include "gnunet/platform.h", but instead include your own config.h and your own system headers. gnunet/platform.h is for this very reason not #included in any of our usual exported headers, and not considered one of our APIs. It includes the platform-specifics of this GNUnet installation. So indeed the answer is to simply not include it, you should not need it to interact with GNUnet!
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
