| Re: Pros & cons of methods 1) DLM and 2) Call_External of calling C from IDL [message #93492 is a reply to message #93489] |
Thu, 04 August 2016 16:11   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On 8/4/16 7:23 am, neil.a.salmon@gmail.com wrote:
> Thanks Mike and Nata,
>
> however, i'm still a bit stuck; typing the following gives:
>
> IDL> help, !make_dll, /structure
> ** Structure !MAKE_DLL, 4 tags, length=48, data length=48:
> COMPILE_DIRECTORY
> STRING 'C:\Users\Neil\.idl\idl_6_0_Win32_x86_m32_f64\c'...
> COMPILER_NAME STRING 'Microsoft Visual C++ 7.0'
> CC STRING 'cl %X -D_DLL -DWIN32 -D_MT /nologo /I"C:\Progr'...
> LD STRING 'link /out:%L /nologo /nodefaultlib /dll %O /de'...
>
> so i guess this means MSVC 7.0 was used to compile the IDL Version 6.0 which i'm running?
>
> As far as i see the COMPILE DIRECTORY is where IDL keeps you own
> complied stuff. However, does this mean there is a MSVC 7.0 lurking
> in either the MS directories or the RSI directories in Program Files
> (x86), ready to be used when you type make_dll?
>
> As far as i know i only a have an MSVC 10.0 compiler and it's not in
> the , C:\Users\Neil\.idl\idl_6_0_Win32_x86_m32_f64\c'... directory.
> Currently make_dll does not compile anything. How should make_dll
> known the path and the file name of the C compiler?
>
> many thanks, Neil
Those are the values for the default compiler on your system. Set them
as needed for your compiler.
Mike
--
Michael Galloy
www.michaelgalloy.com
Modern IDL: A Guide to IDL Programming (http://modernidl.idldev.com)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
