Size of sources

Home Forums Forum Size of sources

This topic contains 2 replies, has 2 voices, and was last updated by  Ellen 6 years, 8 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #79690


    Hey, I’m quite keen on using ellcc for a personal use system I’m building (something like a meld of TinyCore, LFS, and a few other ideas), however I’m on an extremely tight budget regarding data (internet is extremely expensive in my country). So I’m wondering if someone could give me some idea of how large the sources are. Also, if they are larger than around 80MB, is a stripped down version possible for use as a standard system cross/compiler?



    Hi Ellen,
    I have some bad news and some good news. First the bad news. The current full ellcc source tree is about 2G. That contains the sources for all the components used to make ellcc. More bad new is that current binary only downloads are about 700MB.

    The good news is that I’m in the process of retooling the build process and will be updating the binary download packages as well. The ellcc source download will become very small since the new build process will download the needed source files on demand. You’ll only need to download them if you want to build ellcc from scratch.

    I’m also going to trim down the size of the binary downloads. Much of the size in the binary downloads is because they come with precompiled libraries for all the cross targets. With the next release, libraries will be supplied for the host system and you’ll be able to build libraries for other target systems when you need them.

    I’m working on a new release with these changes right now. I’m hoping to have the release ready by the end of the week.




    Thank you, that is excellent news! I’m very glad to have found your project as I’d been trying to work out how to build a musl clang toolchain for my purposes and quite honestly don’t have the expertise to do so. Thank you for providing this. 🙂

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.