fsw.fb fsw...@comcast.net wrote:
(04/04/2009 03:06)
Hi,
if you want to stay with Win32 then you could look for theForger's Win32
API tutorial here:
http://www.winprog.org/tutorial/
That one's really good. I like the humour too. And I just read the appendix on
API vs MFC. Very useful, this
David Raulo wrote:
Hi,
I am a user of the libtcc API; the code I'm working with comes from the
tip of git://repo.or.cz/tinycc.git
Here is a test case which causes a crash under MSVC; it seems to pass
under Linux, except if you take a closer look with valgrind
(see attached file
Pedro A ARANDA wrote:
Hi
the current git version of TinyCC chokes at one of my scripts:
p...@paag:~.../Devel$ syncp tinycc_1.0.0-pre2_i386.deb /media/Philips\
External\ Hard\ Disk/
In file included from /home/paag/bin/syncp:16:
/usr/include/regex.h:543: identifier expected
patch pushed at
http://repo.or.cz/w/tinycc.git?a=commit;h=162e3a937c95cf1912a78d05ffef09b63ca02bd5
--- grischka
Sandor Zsolt wrote:
1. The tcc compiler can`t work with absolute defined include paths.
Solution: in tcc.c in function preprocess from the line 3063
/* now search in all the
lostgallifreyan wrote:
Still, maybe -rdynamic needs more explanation with TCC. So please feel
free to suggest some addition to the docs, say, one short sentence,
placed to your choice ;)
I can try...
Perhaps somewhere in Quick start section, under the Here are some examples
to understand the
grischka gris...@gmx.de wrote:
(04/04/2009 16:40)
As people seem consequently to ignore what's called readme.txt,
meybe we should just get rid of it and have some Windows section
in tcc-doc.html, respectively extend what's already there:
(5.3 PE-i386 file generation)
I think that might partly
