Note: please review and accept the bash-completion pull request (#319) before this one. This issue was forked from that, so it has those commits too.
Description:
FLiT Bisect: Added flags --ldflags, --add-ldflags, and --use-linker
--ldflags: override the linker flags used for the bisect target of the FLiT Bisect Makefile (default is to use the baseline compiler link flags from flit-config.toml)
--add-ldflags: add to the linker flags (instead of override) used for the bisect target of the FLiT Bisect Makefile
--use-linker: provide a different compiler for linking the bisect target of the FLiT Bisect Makefile. The default is the baseline compiler. If --ldflags is not specified, and the compiler provided here is found in flit-config.toml, then the linker flags will be pulled from flit-config.toml.
Other things I changed:
Add BISECT_LDFLAGS to the Bisect Makefile. Used when linking the `bisect target
Make the targets trouble and trouble-fpic only create the trouble object files instead of a trouble executable in the bisect directory. This is mainly because it was hard to decide which set of linker flags to use for the trouble compilation. Also, the only reason we have the trouble target is for precompiling object files, so linking an executable is actually a waste.
Add the new flags to the bash-completion
Documentation:
Added a little blurb in the section about flit bisect saying there are these three flags. It says to see more information, try flit help bisect or flit bisect --help. It is fully documented there.
Tests:
Added a new test called tst_bisect_linkstep.py testing all of these three flags in different combinations.
Fixed one other test that failed because the trouble target was never linked into an executable (tst_bisect_autosqlite_clang.py).
Fixes #308
Note: please review and accept the bash-completion pull request (#319) before this one. This issue was forked from that, so it has those commits too.
Description:
FLiT Bisect: Added flags
--ldflags,--add-ldflags, and--use-linker--ldflags: override the linker flags used for thebisecttarget of the FLiT Bisect Makefile (default is to use the baseline compiler link flags fromflit-config.toml)--add-ldflags: add to the linker flags (instead of override) used for thebisecttarget of the FLiT Bisect Makefile--use-linker: provide a different compiler for linking thebisecttarget of the FLiT Bisect Makefile. The default is the baseline compiler. If--ldflagsis not specified, and the compiler provided here is found inflit-config.toml, then the linker flags will be pulled fromflit-config.toml.Other things I changed:
BISECT_LDFLAGSto the Bisect Makefile. Used when linking the `bisect targettroubleandtrouble-fpiconly create the trouble object files instead of a trouble executable in the bisect directory. This is mainly because it was hard to decide which set of linker flags to use for the trouble compilation. Also, the only reason we have the trouble target is for precompiling object files, so linking an executable is actually a waste.Documentation:
Added a little blurb in the section about
flit bisectsaying there are these three flags. It says to see more information, tryflit help bisectorflit bisect --help. It is fully documented there.Tests:
Added a new test called
tst_bisect_linkstep.pytesting all of these three flags in different combinations.Fixed one other test that failed because the trouble target was never linked into an executable (
tst_bisect_autosqlite_clang.py).