| Re: Pros & cons of methods 1) DLM and 2) Call_External of calling C from IDL [message #93487 is a reply to message #93486] |
Wed, 03 August 2016 06:19   |
Michael Galloy
Messages: 1114
Registered: April 2006
|
Senior Member |
|
|
On 8/3/16 5:21 am, neil.a.salmon@gmail.com wrote:
> Mike,
>
> thanks very much for the offer of the modules. I think for the time
> being i'll take the simple approach, and as i'm working with IDL 6.0
> i'll use the make_dll routine. However with this, how do i tell IDL
> where the compiler is? There are a number of compilers on my machine
> that i know about: MS Visual Studio 10.0, MINGW gcc and g++, and
> TDM-GCC 64\gcc and g++. The directories where the gcc and g++
> compilers reside is in the Environment Variable PATH. However could i
> specify compiler location in the IDL routines, or from within the IDL
> IDE? That way i dont have too much stuff in the Environment Variable
> PATH.
>
> I'd prefer to start doing this from within IDL using make_dll just to
> keep things simple, then later i may do from within MSVS do create
> the dll.
>
> Later i'll invest time on the DLM route, as this seems the best way
> if you have many routines, certainly the best route for long term.
>
> many thanks, neil
>
Check out the !make_dll system variable:
IDL> help, !make_dll
** Structure !MAKE_DLL, 4 tags, length=64, data length=64:
COMPILE_DIRECTORY
STRING
'/Users/mgalloy/.idl/idl/compile_dir-118-idl_8_4-darwin-x86_ '...
COMPILER_NAME STRING 'GCC'
CC STRING 'cc %X -arch x86_64 -fPIC -no-cpp-precomp
-dynamic -fPIC -fn'...
LD STRING 'cc -arch x86_64 -bundle -flat_namespace
-undefined suppress'...
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
