This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
building separate bfd
- From: peter matula <xmatul01 at stud dot fit dot vutbr dot cz>
- To: binutils at sourceware dot org
- Date: Tue, 08 Mar 2011 01:55:13 +0100
- Subject: building separate bfd
Hello,
we are using libbfd in our project to transform various object formats
to our internal format. Because we are working with targets that are not
in default build, it is necessary to build binutils ourselves (we will
append binutils sources to our project).
I have downloaded binutils source code and built it without any problems
with custom targets (--enable-targets). Everything is fine but we in
fact need only libbfd, whole binutils is unnecessary and quite big.
I tried tu separate bfd directory and run ./configure, make, make
install in it. It does not work. Configure is expecting install-sh and
some other files that are not present in bfd subdirectory (only in
binutils/).
In binutils/bfd/README is written: "BFD is normally built as part of
another package". I read guide "to porting the binutils" but there was
nothing about separate build. in fact is seems that it is dependent on
other directories. I tried to find some info in configure and Makefile
files, but those are realy huge and i wasn't able to find out anything
useful.
So I would like to known, is it possible to build sources in bfd
subdirectory separately? If yes, how? If no, how could I at least
minimalize necessary code? Things like gas, readelf, bjdump, ... are
really unnecessary in this case.
Thank you
Peter Matula