Grischka,
First, be sure I don't want to bother you for free. I KNOW for years how to
build and test Windows tcc (both 32/64) from Cygwin32 and Cygwin64 (it was
called win32/Makefile). It allowed anybody to easily test mod changes on
Windows.
My ONLY goal is to let other people to do the same.
grischka wrote:
|Steffen Nurpmeso wrote:
..
|> mildly. I guess the right thing to do would be to strip all paths
|> which are also in the system array from the user paths present in
|> the non-standardized $C_INCLUDE_PATH environment variable, even if
|> that means that
Christian Jullien wrote:
But worse, I've also the impression that, after building W/tcc, make test
still uses Cygwin version. Can you please check and tell me if I'm wrong or
the way I can run "make test" using W/tcc?
Some tests use the build CC (which normally is gcc) to create
the reference
Steffen Nurpmeso wrote:
Hello.
So i thought about it and come back to apologize. At least
mildly. I guess the right thing to do would be to strip all paths
which are also in the system array from the user paths present in
the non-standardized $C_INCLUDE_PATH environment variable, even if
that
Hello.
So i thought about it and come back to apologize. At least
mildly. I guess the right thing to do would be to strip all paths
which are also in the system array from the user paths present in
the non-standardized $C_INCLUDE_PATH environment variable, even if
that means that this possibly