I will not provide with an immediate yes/no answer, but some thoughts on the situation.
Build scripts since many people depend on them should be the most easy to understand area of your code. I would argue that a long "boring" bash should not be an issue as long as it is easily understood. I'd add a hint towards the "configure && build && build install" of the C in various unices.
Your bash script seems to be doing variable initialization and defaults assignment, none of those would get into a deep if-then-else structure.
An estimation of bash scripts size (although it is surely debatable) is that if it is more than 100 lines of code than it might need to be written into a "proper" program. Although the previous sentence is a matter of opinion.
If you decide not to go through the bash route, then you need to get into build tools who are made just for this purpose. Ant / Maven / Gradle in the Java world and many others for different platforms. I can kind of see your example as a series of build targets for some tools I've used in the past, as a sequence of Rake tasks or bazel ones.
I assume that if you go that route then it should be one in the most used language of the project if possible (easier to maintain).
I do not know if there is a name for the field, but someone doing this on day to day basis is called "integration engineer" in some companies.