[haiku-development] Re: Non-standard headers in default compiler search path

  • From: Jérôme Duval <jerome.duval@xxxxxxxxx>
  • To: haiku-development <haiku-development@xxxxxxxxxxxxx>
  • Date: Wed, 15 Apr 2015 19:16:45 +0200

2015-04-14 19:03 GMT+02:00 Adrien Destugues <pulkomandy@xxxxxxxxx>:


1) Remove this from the default include path, and let applications
needing it manually pass the required -I options to the compiler.

2) Protect all the extensions with a define (such as BSD_SOURCE) and
require applications to define that. This is what is done in glibc
(using features.h to control what is or is not included), so it would be
a more usual solution, possibly saving us some work in configure scripts
looking for these extensions. Leave the headers in the standard include
path as they would not define anything anymore without the feature
enabled.

3) Do nothing at all, and be nonstandard. In that case the efforts to
keep everything in separate headers and a separate lib (libbsd) seems a
bit strange to me.


2) would be my favorite.

Bye
Jérôme

Other related posts: