IDL_IDLBridge and IDL8 [message #72664] |
Wed, 29 September 2010 02:37  |
lecacheux.alain
Messages: 325 Registered: January 2008
|
Senior Member |
|
|
When creating IDL_IDLBridge object, I get the following error message:
% Unable to start IDL_IDLBRIDGE slave process.
I am using IDL8 and Windows 64 bits
{ x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010
64 64}
Same code shows no error under IDL7.1 and Windows 32 bits.
What happens ?
alx.
|
|
|
Re: IDL_IDLBridge and IDL8 [message #72712 is a reply to message #72664] |
Mon, 04 October 2010 09:05  |
Michael Galloy
Messages: 1114 Registered: April 2006
|
Senior Member |
|
|
On 10/1/10 1:31 AM, alx wrote:
> On 29 sep, 11:37, alx<lecacheux.al...@wanadoo.fr> wrote:
>> When creating IDL_IDLBridge object, I get the following error message:
>>
>> % Unable to start IDL_IDLBRIDGE slave process.
>>
>> I am using IDL8 and Windows 64 bits
>> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010
>> 64 64}
>>
>> Same code shows no error under IDL7.1 and Windows 32 bits.
>>
>> What happens ?
>> alx.
>
> I answer by myself :
> The statement in error was "s = idl_idlbridge(OUTPUT='toto.log')". The
> cause of the error likely was that the output path must be fully
> expanded and must point to a path with proper access rights, whatever
> the current directory of the calling program is.
> Same behavior under IDL 7.1.
> Therefore, another question will follow: what is the way to provide
> relative paths to idl_idlbridge ?
> alx.
>
FILE_EXPAND_PATH converts relative paths to absolute paths:
IDL> print, file_expand_path('test.log')
/Users/mgalloy/test.log
Mike
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
|
|
|
Re: IDL_IDLBridge and IDL8 [message #72730 is a reply to message #72664] |
Fri, 01 October 2010 00:31  |
lecacheux.alain
Messages: 325 Registered: January 2008
|
Senior Member |
|
|
On 29 sep, 11:37, alx <lecacheux.al...@wanadoo.fr> wrote:
> When creating IDL_IDLBridge object, I get the following error message:
>
> % Unable to start IDL_IDLBRIDGE slave process.
>
> I am using IDL8 and Windows 64 bits
> { x86_64 Win32 Windows Microsoft Windows 8.0 Jun 17 2010
> 64 64}
>
> Same code shows no error under IDL7.1 and Windows 32 bits.
>
> What happens ?
> alx.
I answer by myself :
The statement in error was "s = idl_idlbridge(OUTPUT='toto.log')". The
cause of the error likely was that the output path must be fully
expanded and must point to a path with proper access rights, whatever
the current directory of the calling program is.
Same behavior under IDL 7.1.
Therefore, another question will follow: what is the way to provide
relative paths to idl_idlbridge ?
alx.
|
|
|