[Tcl-bugs] [Tk] (jan.nijtmans) tkt (Closed): Don' t use static libgcc when building as shared lib

[<no...@tc...>]

Automated mail by fx, on behalf of no...@tc...

Ticket Change [5db318af49f5343b897bd26bd045ae2021f7c5003cd63f8597ada538f4dc7437]
  [Don't use static libgcc when building as shared lib]
  By      jan.nijtmans
  For     Tk
  On      2025-10-27T09:00:15.972
  Details https://core.tcl-lang.org/tk/tinfo?name=5db318af49f5343b897bd26bd045ae2021f7c5003cd63f8597ada538f4dc7437
  Ticket  https://core.tcl-lang.org/tk/tktview/71b6efd8f0ac51bf56a5e944f3128a1df9901191

Changed Fields
  assignee:   jan.nijtmans
  closedate:  2025-10-27 09:00:15
  closer:     jan.nijtmans
  foundin:    8.6
  icomment:   This one is also intentional.

              When building Tcl in any environment, it should be possible to copy
              the tclsh executable and the dll's (e.g. with an installer) to another
              machine, and it works. If you don't compile with -static-libgcc, an
              additional dependency with a Mingw-dependant dll is created (I don't
              remember which one).

              A Visual Studio compiled version of Tcl only needs tcl86.dll,
              zlib1.dll (and libtommath.dll, for 9.0+). So if we want to make
              gcc/clang's version of tcl86.dll a drop-in replacement for the Visual
              Studio build of tcl86.dll, we need -static-libgcc. It only makes the
              dll a tiny bit larger.

              So, sorry, I have to reject this ticket as well :-(

              I fully understand that in a MSYS2/Mingw environment, you want to make
              a different choice.
  login:      jan.nijtmans
  resolution: Rejected
  status:     Closed

------------------------------------------------------------
See Tcl/Tk development @ http://core.tcl-lang.org/
------------------------------------------------------------