Can run any recent demo because d3dcompiler_47.dll is missing
category: general [glöplog]
Yep and it is also probably OK for the "safe", uncompressed version.
Dudes, please get your facts straight: For intros dynamically linking to msvcrt is not allowed according to the compo rules of most parties. Check this year's revision compo rules for example.
This has been discussed a lot in the past. Thank god it stayed like this.
This has been discussed a lot in the past. Thank god it stayed like this.
https://2016.revision-party.net/compos/pc
They explicitly mention that no msvcrt dlls will be present on the compo machines.
They explicitly mention that no msvcrt dlls will be present on the compo machines.
it's a major pain to try and find a friend without visual studio to test a demo tho, only the compo machine doesn't have the dlls
spike: I think people are referring to "the" MSVCRT.DLL that ships with Windows since forever, not the CRTs of later Visual Studio versions.
omg. just copy it from a redist- you all industry fux tell microsoft to include all of the goods. 47 works on 7 same as the old d3dx works on 10. why the office jerks don't include that? damn jerks. it makes everybody's code a lil easier. -_-
Quote:
Dudes, please get your facts straight: For intros dynamically linking to msvcrt is not allowed according to the compo rules of most parties. Check this year's revision compo rules for example.
This has been discussed a lot in the past. Thank god it stayed like this.
You cannot link to MSVCRT.DLL even though thats a Windows XP component?
more or less every new visual studio release comes with a new version of msvcrt.dll.
which means that if you build your demo/intro with VS 2015 for example, a person that has a standard win7 installation (without the VS2015 runtime libraries) will not be able to run your exe. Even if he has installed a earlier version of VS, because that will use a different msvcrt dll.
1) I want my demos to be viewed as hassle-free as possible. Forcing people to download stupid DLLs first will limit your audience. I want to show demos to uninitiated people, who don't care about DLL issues.
2) Dynamically linking 64k/4k intros to msvcrt will potentially give you more bytes for intro code, which changes the game and reduces the possibility to compare apples to apples i.e. old intros to new intros
which means that if you build your demo/intro with VS 2015 for example, a person that has a standard win7 installation (without the VS2015 runtime libraries) will not be able to run your exe. Even if he has installed a earlier version of VS, because that will use a different msvcrt dll.
1) I want my demos to be viewed as hassle-free as possible. Forcing people to download stupid DLLs first will limit your audience. I want to show demos to uninitiated people, who don't care about DLL issues.
2) Dynamically linking 64k/4k intros to msvcrt will potentially give you more bytes for intro code, which changes the game and reduces the possibility to compare apples to apples i.e. old intros to new intros
what is the problem with vcrt tho? i know that issue to download new versions of runtime again and again. piling up in my software list. that crap. just like windows balloony tho anyway. typical microshit. but...
why can i not call any vcrt version that might be installed from within an intro? why does it not work? anybody knows? what does that manifest matter? afaik it's always the same push call assembly code. the dll code should expect fixed input. why it needs a version? is it microshit? that code logic sux. gotta blow them up. you know that. anybody demosceners working there tell them that they're doing bullshit. there gotta be better ways. :D
why can i not call any vcrt version that might be installed from within an intro? why does it not work? anybody knows? what does that manifest matter? afaik it's always the same push call assembly code. the dll code should expect fixed input. why it needs a version? is it microshit? that code logic sux. gotta blow them up. you know that. anybody demosceners working there tell them that they're doing bullshit. there gotta be better ways. :D
Quote:
more or less every new visual studio release comes with a new version of msvcrt.dll.
which means that if you build your demo/intro with VS 2015 for example, a person that has a standard win7 installation (without the VS2015 runtime libraries) will not be able to run your exe. Even if he has installed a earlier version of VS, because that will use a different msvcrt dll.
Again, especially for tinytros it has long been established to use the system-provided MSVCRT.DLL rather than the VS-specific MSVCRT*.DLL with a number (e.g. MSVCRT10.DLL for VS2010). What you say is true for all systems, the newer CRTs are not shipped with any Windows version. Officially, MSVCRT.DLL is not part of the operating system and only "for internal use", but it has been there since forever so people started linking against it.
Quote:
what is the problem with vcrt tho? i know that issue to download new versions of runtime again and again. piling up in my software list. that crap. just like windows balloony tho anyway. typical microshit. but...
Yeah, because C runtimes and library versioning are a Windows-only thing. Oh wait...
<°)))><
