On Sep 18, 2014, at 3:12 AM, Richard Earnshaw <rearn...@arm.com> wrote:
>
> Is there any real need to write this into the source directory and have
> the built file checked in? Ie. can't we always write to the build
> directory and use it from there.
I build part of my .md file from a C++ program, so I have to build that
program, then generate the md file:
s-mddeps: abi.md
abi.md: s-abi; @true
s-abi: genmd $(srcdir)/config/port/port-assist.h
./genmd >tmp-abi.md
$(SHELL) $(srcdir)/../move-if-change tmp-abi.md abi.md
$(STAMP) s-abi
genmd: $(srcdir)/config/port/genmd.c $(OPTIONS_H) s-genbuiltin
touch insn-constants.h
touch insn-flags.h
$(COMPILER_FOR_BUILD) $(BUILD_COMPILERFLAGS) $(BUILD_CPPFLAGS)
$(srcdir)/config/port/genmd.c -o genmd
Certainly bash source is portable enough to just built on demand. This let’s
me take content that is in .h files concerning the abi and generate md
constants from them.
