Comment Re:I don't understand the issue (Score 1) 753
The 64-bit linker can link 32-bit object files, albeit without link-time code generation.
The 64-bit linker can link 32-bit object files, albeit without link-time code generation.
Here: http://msdn.microsoft.com/en-us/library/5wy54dk2(v=VS.80).aspx
Ah, sorry -- I see the difference now, you're using link time code generation which the x64 bit linker is not capable of when the machine type is x86.
hello.c:
#include
#include
int main(int argc, char *argv[])
{
printf("Hello world!\n");
return EXIT_SUCCESS;
}
hello.bat:
@ECHO OFF
SETLOCAL
CALL "%VS80COMNTOOLS%..\..\vc\vcvarsall.bat" x86
cl
ENDLOCAL
SETLOCAL
CALL "%VS80COMNTOOLS%..\..\vc\vcvarsall.bat" amd64
link
ENDLOCAL
output:
C:\Project>hello.bat
Setting environment for using Microsoft Visual Studio 2005 x86 tools.
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.
hello.c
Setting environment for using Microsoft Visual Studio 2005 x64 tools.
Microsoft (R) Incremental Linker Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.
C:\Project>hello.exe
Hello world!
You might want to look into the
Why can't you use the 64-bit toolchain from VS2005 to produce 32-bit binaries?
Are you dumb?
You're wrong, you can easily output 32-bit binaries with a 64-bit toolchain with MSVC - even from within the Visual Studio IDE if you set up the environment from the command line and then type "devenv
The future of rendering in video games has always been evident if you look at high-end rendering for films. If you look at a product like Renderman, ray-tracing is used for specific materials in the scene, but not commonly used for rendering the whole frame. Getting realistic materials out of the renderer is the real problem, not rendering mirror balls.
So, Deepwater Horizon (and hundreds of other smaller disasters, still with larger environmental impact than the Fukushima incident) never happened?
The reality is that nuclear is safer than oil, and yet there is so much fear, It's like airplanes, occasionaly one falls down and people are afraid of flying even though it is 100x safer than driving a car which people do every day without fear.
I'm working in a company that does Scientific Visualization, and we have driver issues on a regular basis and have to find workarounds for them. It's a big pain to do testing with all kinds of different configurations and try to work around the problems in the drivers. The reason you don't have driver issues is because you play games and the poor graphics programmers have had to work around all the issues in the drivers you're running. If you have some combination of driver/graphics card that the developers didn't test, chances are you're going to have issues.
Honestly, I would pick Visual Studio / C#
I've done a bit of C# programming recently and I expected to hate it, since I'm not a big fan of Java and everyone were telling me it is a similar language. However it's proven to be a wonderful experience, the
XCode is getting better now that they are moving over to the clang/LLVM toolchain instead of gcc. It will eventually let Apple provide a good IDE experience which has never been the goal of gcc/gdb. Unfortunately Objective-C is not a modern programming language and Apple really needs a strategy for a next generation programming language. Here's to hoping they adopt C# and make a C#/Cocoa alternative to C#/.NET (probably right about the time hell freezes over).
8 Catfish = 1 Octo-puss