Archives of the TeradataForum

Message Posted: Sun, 03 Feb 2008 @ 09:22:53 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

We should also note that you need to adjust the compiler path settings / registry settings to match the version of the compiler you installed. In the registry settings, use the "7.1" keys, but true paths in the values.

For example, I installed Visual C++ Express 2005 as a C/C++ compiler on my machine. Here were my settings:

     _cufconfig_
     CompilerPath: C:\Program Files\Microsoft Visual Studio 8\VC\bin\CL.EXE
     LinkerPath: C:\Program Files\Microsoft Visual Studio 8\VC\bin\LINK.EXE

     _registry _
     Windows Registry Editor Version 5.00

     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1]
     "InstallDir"="C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\IDE\\"

     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Setup]

     [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\Setup\VC]
     "ProductDir"="C:\\Program Files\\Microsoft Visual Studio 8\\VC\\"

With regard to copying "nmake" around, the important thing is that the "nmake" executable and any DLLs it depends on are in the system path (somewhere in the System PATH environment variable). To accomplish this, I manually added the Visual C++ "bin" directory to my path.

_Another Note for VC++ 2005 & 2008_

You can add parameters that will always be passed to the compiler and linker in these two system variables:

     CL - compiler command line options
     LINK - linker command line options

Using the VC++ 2005 compiler, I had trouble compiling UDFs unless I specifically added "libcmt" (or another C runtime library) as a Shared Library to be compiled with the UDF source code. I got around this by adding "libcmt.lib" to my system-level "LINK" environment variable - so that this library is always explicitly compiled in.

- Chris

	<Prev	Next>		<<First	<Prev	Next>	Last>>