Hi Kaz,

With the generated gnumake and empty environment, especially wo cygiwn
Using this Makefile:

all:
        tcc -v
        dir *.exe

I tried the following:

F:\tinycc\win32>set SHELL=
F:\tinycc\win32>echo %SHELL%
%SHELL%
F:\tinycc\win32>gnumake
tcc -v
tcc version 0.9.27 (x86_64 Windows)
dir *.exe
 Volume in drive F is New Volume
 Volume Serial Number is 12C9-E1B4

 Directory of F:\tinycc\win32

2020-01-22  18:58           331,776 gnumake.exe
2020-01-22  17:01           254,464 i386-win32-tcc.exe
2020-01-22  17:01           320,512 tcc.exe
2020-01-22  17:01           320,512 x86_64-win32-tcc.exe
               4 File(s)      1,227,264 bytes
               0 Dir(s)  112,570,724,352 bytes free

F:\tinycc\win32>echo %SHELL%
%SHELL%

So it works perfectly as minimal C environment with a decent make utility. The 
.zip archive (C 32+64bit compiler, linker, includes and gnumake.exe) is less 
than 1Mb

2020-01-22  17:00           983,821 tcc-0.9.27-2020-01-13-x86_64-win32.zip


-----Original Message-----
From: Kaz Kylheku (gmake) [mailto:729-670-0...@kylheku.com] 
Sent: Wednesday, January 22, 2020 19:15
To: jull...@eligis.com
Cc: help-m...@gnu.org; tinycc-de...@nongnu.org
Subject: Re: I want to port make on Windows using tcc compiler

On 2020-01-22 05:38, Christian Jullien wrote:
> To provide a complete working C toolchain, it lacks a 'make' utility as 
> with
> other unix like systems.

Don't forget that make recipes are written in shell (by default; there 
is a SHELL variable).

So if you compile make successfully, but haven't provided a shell, you 
still can't process the usual shell-based makefiles.

[Not sure it's such a great idea to cross-post between tinycc-devel and 
help-make, but I'm preserving the Cc: line.]




Reply via email to