Hi Anthony,
I am also doing shaders with VC++ 8 (Visual Studio 2005 Express in my case) and they work just fine in XSI. Just make sure you include the needed runtime-Dlls with the shader or point to a redistributable download package at the MS site so the users can get them easily. Microsoft doesn't just "increment the filename", but includes new features etc. and those new runtime Dlls can reside next to the old ones without much problem. Basically it is the same as with a tool like XSI 5 including new features over XSI 4... Which isn't such a bad thing ;-)
But sure you can use VC 6 or 7 for easier compatibility, since more people have those older runtime libraries already installed. But this is a problem that will solve itself over time when more apps use the newer compilers.
Cheers,
Thomas Helzle
On Sun, 26 Feb 2006 19:33:54 +0100, Anthony Rossano <anthor(at)mesmer.com> wrote:
Hi All -
I thought I would get adventurous and compile some shaders with Visual
Studio .Net. It had recently upgraded itself and the .Net framework.
The resultant shaders would not run on client machines because they
were linked against MSVCRT8.dll.
It seems that MS like to increment the name of the DLL periodically,
which is trouble since it makes the shaders compiled with the new .net
incompatible with all prior versions of Windows.
So, the question is, does anyone know how to get Vis. Studio .Net to
link against a prior version of the MSVCRT Dll?
The wiki is woefully limited on the topic of compiling shaders, though
it suggests that VS .Net is the preferred compiler.
I myself have found VC 6.0 to be the choice that actually works.
Help on what windows compiler to use, and the MSVCRT issue from anyone
out there?
ATR
[ Anthony Rossano ]
- COO, IOACTIVE -
- CEO, Mesmer Inc -
http://www.ioactive.com
http://www.mesmer.com
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
