Displaying 2 results from an estimated 2 matches for "link_input".
Did you mean:
link_inputs
2008 Apr 29
0
[LLVMdev] Representing the dependencies of a bitcode module
...n't matter if you think it through.)
Granted that you're not using make, but the principal is perfectly
sound.
For linkage command lines, lazily updating 'response files' (sorry,
Windows terminology...) can provide a complete solution. Something like:
LINK_CMD := $(LINKER) $(LINK_INPUTS)
all: cmds
link_cmd:
if [ "`cat $(INT_DIR)/link_cmd`" != "$(LINK_CMD)" ]; then echo "$
(LINK_CMD)" > link_cmd; fi
output.so: link_cmd $(LINK_INPUTS)
$(LINK_CMD)
Of course, these are complimentary depending on your needs. Using a
response file for compilati...
2008 Apr 29
3
[LLVMdev] Representing the dependencies of a bitcode module
I've been using SCons as the build tool for my frontend application, and
I'm getting to the point where it would be useful to create a custom
scanner for my generated bitcode files so that SCons can do proper
dependency analysis. At the moment, SCons has no way to know which
source files a particular bitcode file depends on, so the only way to do
a "correct" build is to