re-run build-toolchain

We have pre-built tool chain for Windows and Linux. You can just use them directly. The build-toolchain script is only for someone who want to build tool chain from our source packages.

Yes, I know. I do use the pre-built version. But it does not yet support TMS570 (see #189066).
So I wonder if I need to re-run the complete build script if I change some setting (newlib gcc)
(A build takes quiet long).

Depends on your changes, ideally you can just recompile things you changed, but it is complicated to figure out which one are needed and which one aren't needed. So in this case, I would like to recommend you to rebuild the tool chain with your own changes. There is a document named How-to-build-toolchain.pdf which you can find out how to do this. Be aware that the build-prerequisites.sh should be performed firstly to build all supporting libraries.

Sorry, I seem to express my-self bad.

I have setup a environment like it is described in the how-to. But running the build-toolchain script takes long.

I wonder, if it is possible to do a "make" after changing sources, so that only the relevant parts are rebuild, or do I have to rebuild _all_, which took on my (virtual) machine nearly 3 hours.

Can you give more details on what you are changing. You want a tool chain for Linux or Windows?

Hi,

I'd like to play with the multilib option. But it seems, I need to dig through the script and disable the "rm -rf" parts.
I just wondered, do you ("the maintainers") always do a complete re-build ? Or are you using different scripts.
I am trying "make" in build-linux/gcc-final".
(In the end, I'd like to have a MinGW build, yes).