This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: opcode headers
- From: Jeff Johnston <jjohnstn at redhat dot com>
- To: Alexander Fedotov <alfedotov at gmail dot com>
- Cc: Newlib <newlib at sourceware dot org>
- Date: Tue, 20 Mar 2018 12:54:21 -0400
- Subject: Re: opcode headers
- References: <CAN8C2CoCWrHDE=1Ap3hFETDTv-etj78G1vwEFCaWP=8ROg1q6g@mail.gmail.com>
Newlib has shared folders with other sourceware projects such as gcc, gdb,
and binutils. They are maintained in their
respective projects and copied. If you take a look at the top-level
MAINTAINERS file you can see where you must send changes
to such shared files. Just because they are shared doesn't mean they are
used by every component. However, if you wanted to
merge to create a unified source directory that could build multiple
components (e.g. gcc, newlib, binutils), you only need to link in the
non-shared
folders into one. See https://sourceware.org/newlib/faq.html#q3
-- Jeff J.
On Tue, Mar 20, 2018 at 6:39 AM, Alexander Fedotov <alfedotov@gmail.com>
wrote:
> Can anyone explain for what purpose opcode headers from binutils are
> living in "/include/opcode" folder?
>
> Best regards,
> Alex
>