On Fri, Sep 29, 2017 at 7:17 AM, Christian JULLIEN <address@hidden
> Ok I understand,
> What annoys me is that I must install i686-w64-mingw32-gcc I don't really
> care just to compile tcc for native Windows while std cygwin/gcc is
> perfectly able to do the same.
My effort to make tcc build in cygwin rather as a cross-compiled
native windows application has been on hold for about a year
pending the new release of tcc.
I would classify using cygwin to build a mingw compiled tcc is just
cross compiling from cygwin to win32.
As a long time cygwin user the single configuration "technique"
that is a problem for a working cygwin/posix port is to "look underneath"
the cygwin posix environment to "discover" the native win32 beneath
and to build for that. The correct approach is to detect cygwin as
a flavor of unix and treat it as such.
I'm looking forward to the coming stable release. Exciting
to see we're getting close.
> I'll try use main Makefile and see what is actually missing compared to
> win32/Makefile to produce Windows native tcc for both x86 and x64.
> You can remove win32/Makefile if you like, I'll survive w.o. it :o)
> Le : 29 septembre 2017 à 10:46 (GMT +02:00)
> De : "grischka" <address@hidden
> À : "Christian Jullien" <address@hidden
> Cc : "'avih'" <address@hidden
> Objet : Re: [Tinycc-devel] Push reproducible builds script? (for windows)
> Christian Jullien wrote:
>> I can try to detect CYGWIN_NT* from main Makefile and recursively call
>> $(MAKE) -C win32
> No, Christian. I finally decided to scrap the win32/Makefile.
> It will not be part of the release.
>> /cygdrive/f/tinycc$ ./configure
> No. As I already wrote, the cross-compiler prefix of cygwin's
> "GCC for Win32 Toolchain" (a.k.a. mingw-gcc) needs to be passed
> to configure:
> configure --cross-prefix=i686-w64-mingw32-
> configure --cc=i686-w64-mingw32-gcc
> The prefix may vary depending on cygwin version.
> Btw. to manage the win32 target with its own Makefile would of course
> be possible, but does make sense only if it works on all systems and
> hence can at the same time simplify the main Makefile to at least the
> same extend. I can't say how well this would work but anyway it's too
> late now to try for this release.
> Best regards,
> --- grischka
> Tinycc-devel mailing list
Tinycc-devel mailing listaddress@hiddenhttps://lists.gnu.org/mailman/listinfo/tinycc-devel