项目作者: napi-bindings

项目描述 :
GCC compiler, Windows-friendly.
高级语言: C
项目地址: git://github.com/napi-bindings/tdm-gcc.git
创建时间: 2020-06-04T00:31:47Z
项目社区:https://github.com/napi-bindings/tdm-gcc

开源协议:Other

下载


TDM-GCC

This repository contains an unofficial binary distribution for TDM-GCC compiler.

This distrubution is internally used for some napi-bindings projects.

Version 10.3.0

GitHub All Releases
GitHub release (latest by date)

COPYING

To the extent possible under law, the author(s) have dedicated all copyright and
related and neighboring rights to this software to the public domain worldwide.
This software is distributed without any warranty.

You should have received a copy of the CC0 Public Domain Dedication along with
this software. If not, see http://creativecommons.org/publicdomain/zero/1.0.

PACKAGE CONTENTS

This is the set of scripts and miscellaneous files used to drive the build
systems of all components that create the TDM-GCC toolchain. It includes a
Makefile with targets for the TDM and TDM64 editions of GCC and all support
libraries, and .sh script files that invoke the Makefile with appropriate
arguments for each TDM-GCC edition.

Patches for the underlying binutils, GCC, GDB, and winpthreads components used
to be included as part of a combined TDM source and build scripts release
tarball, but are now kept in individual Github.com source repositories per
component:

ADDITIONAL REQUIREMENTS

In order to duplicate the build process used for TDM’s binaries, you will need
the following packages:

BUILD NOTES

The 10.3.0 TDM32 and TDM64 GCC binaries were built as native bootstraps in
Windows 10 (64-bit), using previously built toolchains with the same set of
patches, under the MSYS2 environment. The build
scripts in this package will probably not work in Cygwin, WSL, or GNU/Linux
without modification.

Generally, building GCC consists of first building its support libraries (gmp,
mpfr, mpc, isl, libiconv, winpthreads, and windows-default-manifest), combining
these with binutils and the runtime API into the “staging prefix”, and then
building GCC itself. GCC is built to expect it will be installed to the staging
prefix but for the installation step is actually staged into a different
directory.

Building the TDM32 edition typically looks like this:

  • Extract all sources to /crossdev/src
  • Copy or build a previous MinGW installation to a “build toolchain”
  • Bootstrap the MinGW.org mingw-get installer into /crossdev/gccmaster/mgbase
  • Ensure the prefix, typically /mingw32tdm, is empty
  • ./tdm32.sh

Building the TDM64 edition typically looks like this:

  • Extract all sources to /crossdev/src
  • Copy or build a previous multilib MinGW-w64/GCC installation to a “build
    toolchain”
  • Ensure the prefix, typically /mingw64tdm, is empty
  • ./tdm64.sh