My first demo, yeah!
category: offtopic [glöplog]
Runs here - with tearing from hell...
i support every newcomer as it looks now the demoscene is a bunch of middle-agers who cannot really decide between keyboard and pampers. ^^
Thanks for the help, i will update it with the nondll version, so everybody without the Microsoft SDK can use it :D
You're lucky...
Cause music is half of the demo...
And music is damn good.
:)
Cause music is half of the demo...
And music is damn good.
:)
4. Allow your intro to require msvcrt2010: http://www.microsoft.com/download/en/details.aspx?id=5555
Its 2012 FFS. Why code like its 2004? You dont save any space of significance by using it. Shitloads of applications we use already require the dlls anyway. So its a big chance its already installed. Moreso than directx dlls, for instance.
Douchebags kan keep fooling themselves that a production that caters to the 'old more elegant, idealistic' standards are better and everything else sucks. The rest of us just wants to see more new 64ks. Making 64ks are time consuming enough without dealing with details that really belongs in the 4k category. Especially for newcommers.
Its 2012 FFS. Why code like its 2004? You dont save any space of significance by using it. Shitloads of applications we use already require the dlls anyway. So its a big chance its already installed. Moreso than directx dlls, for instance.
Douchebags kan keep fooling themselves that a production that caters to the 'old more elegant, idealistic' standards are better and everything else sucks. The rest of us just wants to see more new 64ks. Making 64ks are time consuming enough without dealing with details that really belongs in the 4k category. Especially for newcommers.
@Blacksheep8Bit: if you don't understand linking and the Windows system well enough yet, maybe you should forget about the size coding for now and wait to get more comfortable first.
Still if you're curious you should definitely have a look at IQ's 64k framework, which compiles out of the box with VS 2008 (I don't know if it would work with an automatic VS2010 conversion though). See how it manages to get rid of the standard library and reimplements it, and also how much work it is. ;)
Still if you're curious you should definitely have a look at IQ's 64k framework, which compiles out of the box with VS 2008 (I don't know if it would work with an automatic VS2010 conversion though). See how it manages to get rid of the standard library and reimplements it, and also how much work it is. ;)
Runs here, Win7 x64 ATI HD5850.
Thanks 4Tey.
Works here Windows 7 ATI Radeon HD 5570
Works here Windows 7 ATI Radeon HD 5570
Gargaj: I know. I dont have to like it though.
While those IQs and Chaos sources are great there are more issues to deal with when removing the dlls. On the top of my head you have global constructors, vtables, various sneaky STL features, rounding for /QIfist and the list goes on. And they tend to pop up again and again. Its not really a solve-once issue.
I say allow them runtime libs. They dont help production in any way but comfort and compatibility. Compare it to dos4gw of the msdos era. Also, the corresponding static build might be huge but this size has no bearing. In almost every case eliminating this dependency actually saves size. But, IMHO, finishing the intro is more important than ideal size or perfect enduser convenience (which will be leaps and bounds better than most 4ks anyway).
While those IQs and Chaos sources are great there are more issues to deal with when removing the dlls. On the top of my head you have global constructors, vtables, various sneaky STL features, rounding for /QIfist and the list goes on. And they tend to pop up again and again. Its not really a solve-once issue.
I say allow them runtime libs. They dont help production in any way but comfort and compatibility. Compare it to dos4gw of the msdos era. Also, the corresponding static build might be huge but this size has no bearing. In almost every case eliminating this dependency actually saves size. But, IMHO, finishing the intro is more important than ideal size or perfect enduser convenience (which will be leaps and bounds better than most 4ks anyway).
Yomat: not saying you should or shouldn't like it, but part of the problem is that e.g. kkrunchy doesnt have the same error mechanism as crinkler does for showing if a DLL is missing, instead it just crashes and it's up to the coder to figure out why. :/
Works smoothly on Linux with Wine 1.4, ATI Radeon HD 6320
