Xianwen,
- "libmaker" in my batch file is the same as tiny_libmaker from
the 0.9.25 distribution.
- Assuming "old" is the 0.9.25 tcc/win32 directory, and "new" is
where I'm building/testing the new compiler, then what I actually
do is...
$ old\tcc -o tmp_tcc.exe src/tcc.c
This compiles the tmp_tcc with the old tcc. But it's still using
the include files from old/include AND it's grabbing libtcc1.a,
msvcrt.def and kernel32.def from old/lib.
- Then I compile new/(tiny_)libmaker and new/(tiny_)imdef. And I
use (tiny_)libmaker to make new/lib/libtcc1.a. (I usually also
recreate mvscrt.def and kernel32.def from the actual DLLs.)
- Now if you compile a "newer" version of tcc (using new/tmp_tcc),
you'll be picking up the new/include files and the
new/lib/libtcc1.a, and there won't be any vestiges of the old tcc.
Regards,
Tom
Thank you very much Tom. It helped! ;)
Xianwen
|