| Re: again call_external [message #38822] |
Thu, 01 April 2004 09:01 |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
"Valerio Pace" <valerio.pace@fastwebnet.it> wrote in message
news:c4hau0$r4m$1@lacerta.tiscalinet.it...
> Hi all,
>
> I have some big problem to learn how to use the CALL_EXTERNAL function.
> (OS=windows, IDL 5.5)
> I have created my C procedure but I'm not able to call it.
> I try to use MAKE_DLL in this way:
>
> MAKE_DLL, 'myprocedure', 'myprocedure'
>
> but IDL "writes":
> "\Documents" is not an internal or external command, or an exe or batch
> file.
>
> What's my mistake?
This may have been a problem with older versions of IDL. The problem was
dealing with file paths containing space characters. You can upgrade to a
newer version, probably 6.0. Or, try using the COMPILE_DIRECTORY keyword on
MAKE_DLL to change your build directory name so that there are no spaces in
it. Yet another way is to specify NOCLEANUP and then edit the batch file to
add quotes around filenames and run the batch file manually. I'm not
positive that these kwds are in 5.5 though.
> How can I understand if IDL "see" my C compiler (Visual C++ 6.0)?
When you install the Visual C++ compiler, you are prompted for the option of
adding the compiler environment variables to your environment when you login
to Windows. If you said yes, IDL should find your compiler.
If you said no, or don't remember, then try make_dll, after solving the
above problem about spaces in filenames. If you get an error message about
not finding the 'cl' command, you'll need to modify your system environment
variables.
First, locate the batch file that sets the environment variables so that you
can run the Visual C++ compiler from the command line. On my system, it is
C:\msdev\VC98\Bin\VCVARS32.BAT. Open it up and see that it sets the INCLUDE
and LIB env vars and adds the compiler dirs to the PATH.
Now find the applet for changing your environment variables in the Windows
System control panel. Add/modify the environment variables according to the
batch file. After you do this, the batch file generated by IDL to compile y
our files should be able to locate the compiler.
Karl
|
|
|
|
| Re: again call_external [message #38823 is a reply to message #38822] |
Thu, 01 April 2004 08:37  |
Rick Towler
Messages: 821
Registered: August 1998
|
Senior Member |
|
|
"Valerio Pace" wrote...
> Hi all,
>
> I have some big problem to learn how to use the CALL_EXTERNAL function.
> (OS=windows, IDL 5.5)
> I have created my C procedure but I'm not able to call it.
> I try to use MAKE_DLL in this way:
>
> MAKE_DLL, 'myprocedure', 'myprocedure'
>
> but IDL "writes":
> "\Documents" is not an internal or external command, or an exe or batch
> file.
>
> What's my mistake?
> How can I understand if IDL "see" my C compiler (Visual C++ 6.0)?
>
> I've just searched related messages in the newsgroup, but i still haven't
> found what i'm looking for.
I don't use CALL_EXTERNAL but the error suggests that you have a path issue.
It looks like your path is either malformed (should be 'x:\documents' or
'\\documents') or more likely whatever is processing the path doesn't like
spaces so use the 8.1 equivalent (x:\Docume~1\... instead of x:\Documents
and Settings\...)
Check the docs for all references to paths that MAKE_DLL might utilize and
then check those paths.
-Rick
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
