tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Compiling tcc under Windows using tcc?


From: Tom Hartnett
Subject: Re: [Tinycc-devel] Compiling tcc under Windows using tcc?
Date: Mon, 05 Dec 2011 08:55:17 -0500
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0

On 12/4/2011 4:03 AM, Xianwen Chen wrote:
Hi Tom,

Thank you. It is encouraging to know that compiling tcc using tcc is doable and someone else is doing it.

I was actually wondering if you use tcc_libmaker to

libmaker rcs lib/libtcc1.a crt1.o chkstk.o libtcc1.o alloca86.o

Xianwen 

--

Xianwen Chen

 

Dept. of Economics and Resource Management
Norwegian University of Life Sciences
Christian Magnus Falsensvei 18, 1432 Ås, Norway
+1 (307) 223-2122 | address@hidden

 




_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]