[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] On applications using GNUnet
From: |
Christian Grothoff |
Subject: |
Re: [GNUnet-developers] On applications using GNUnet |
Date: |
Tue, 6 Aug 2019 11:07:55 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
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
- Re: [GNUnet-developers] On applications using GNUnet, (continued)
Re: [GNUnet-developers] On applications using GNUnet, t3sserakt, 2019/08/06
Re: [GNUnet-developers] On applications using GNUnet, Christian Grothoff, 2019/08/06
Re: [GNUnet-developers] On applications using GNUnet, Heiko Stamer, 2019/08/07
Re: [GNUnet-developers] On applications using GNUnet,
Christian Grothoff <=
Re: [GNUnet-developers] On applications using GNUnet, Christian Grothoff, 2019/08/06
Re: [GNUnet-developers] On applications using GNUnet, Christian Grothoff, 2019/08/06
Re: [GNUnet-developers] On applications using GNUnet, Christian Grothoff, 2019/08/06