From: Rob Landley:
I'm currently debugging why arm linking isn't working properly (I can build a
hello.o with tinycc and then link it with an armv5l-gcc I have lying around,
but if it links itself the result immediately segfaults under qemu-arm.
...
Well, we didn't hear anything about arm
From: KHMan:
Binary releases calls for certain expectations from their uses.
That is true, also it calls for certain users per se. But why
exclude such users? Programmers writing programs only for
programmers has some boring aspect too, IMO.
On Tue, Mar 4, 2008 at 5:37 AM, grischka wrote:
grischka wrote:
From: KHMan:
Binary releases calls for certain expectations from their uses.
That is true, also it calls for certain users per se. But why
exclude such users? Programmers writing programs only for
programmers has some boring aspect too, IMO.
That was a typo, I meant
Win32 binaries with Win32 Api definitely needed.
The libtcc.a and libtcc.h for dynamically compilation.
On Tue, Mar 4, 2008 at 5:37 AM, grischka wrote:
Should we make a release now?
Any suggestions what to still include with it?
--- grischka
___
Hanzac Chen wrote:
Win32 binaries with Win32 Api definitely needed.
The libtcc.a and libtcc.h for dynamically compilation.
Speaking as a list member, I'll all for more services for users,
but let's be realistic: I don't think this community has the
resources to maintain binary releases. We have
Should we make a release now?
Any suggestions what to still include with it?
--- grischka
___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
