[PATCH] Move 'enum bfd_endian' to a non-generated header
Mike Frysinger
vapier@gentoo.org
Thu Feb 18 16:08:00 GMT 2016
More information about the Binutils mailing list
Thu Feb 18 16:08:00 GMT 2016
- Previous message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
- Next message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 18 Feb 2016 15:15, Pedro Alves wrote: > On 02/18/2016 02:59 PM, Nick Clifton wrote: > > Also - why create a new header file ? Why not just add it to bfdlink.h ? > > > > Unfortunately that wouldn't work, because bfdlink.h depends on types that > depend on bfd being configured. E.g., bfd_vma. since bfd.h is already a generated header from multiple inputs, why not create a new bfd-in-plain.h (or whatever) file that also gets gathered ? then code in-tree can include that directly and out of tree users do not need to change anything. > > (New header files are a pain for toolchain releases and distribution > > packagers). this is significant. off the top of my head, there's a few places in Gentoo i'd have to adjust, and do so dynamically (since we support old versions too). -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <https://sourceware.org/pipermail/binutils/attachments/20160218/c5a6fb53/attachment.sig>
- Previous message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
- Next message (by thread): [PATCH] Move 'enum bfd_endian' to a non-generated header
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list