lostgallifreyan lostgallifre...@gmail.com writes:
You cite from MSDN... I take it this is because TCC defaults to
using MSVCRT? (Or, I read tonight, Kernel32.dll if the program
entry point was written to avoid using MSVCRT).
The Windows GDI functions are in USER32 and GDI32, not MSVCRT.
I
Kalle Olavi Niemitalo wrote:
lostgallifreyan lostgallifre...@gmail.com writes:
You cite from MSDN... I take it this is because TCC defaults to
using MSVCRT? (Or, I read tonight, Kernel32.dll if the program
entry point was written to avoid using MSVCRT).
The Windows GDI functions are in
lostgallifreyan wrote:
Ok, I see that changing
C:\tcc\tcc.exe -I%P%\src -o%P%\bin\lua.dll -shared -rdynamic %P%\src\*.c
to
C:\tcc\tcc.exe -I%P%\src -o%P%\bin\lua.dll -shared -DLUA_BUILD_AS_DLL
%P%\src\*.c
..works as it should without changing the source itself, for Lua.exe anyway.
If I
grischka gris...@gmx.de wrote:
(03/04/2009 14:30)
Well see, Lua is a piece of code with some tens of thousands of lines
where each word is well designed and meaningful with the final binary
product. So if some symbols are exported and others are not then
this is likely not meant to fool
Kalle Olavi Niemitalo k...@iki.fi wrote:
(03/04/2009 09:05)
And that means I'm not sure how I should write any GDI
oriented code if I want it to compile on Linux. I'd thought the
same might apply to both.
Ah, you mentioned GDI resources in your original post, so I
assumed you were intending
KHMan keinh...@gmail.com wrote:
(03/04/2009 10:15)
Apart from the links to Win32 help files that grischka has
mentioned, a alternative that is a little more up-to-date is the
PlatformSDK_Svr2003R2_rtm ISO (just do a Google search). It's
nicely packaged (self-contained, unlike a lot of other
Hi,
if you want to stay with Win32 then you could look for theForger's Win32
API tutorial here:
http://www.winprog.org/tutorial/
There you can not only get a Win32 tutorial, but also some examples (afaik).
Here a short Win32 example:
#include windows.h
const char g_szClassName[] =
