comp.lang.idl-pvwave archive: archive » Resolve_all behaves differently on that command line that in the IDE console

Home » Public Forums » archive » Resolve_all behaves differently on that command line that in the IDE console

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Resolve_all behaves differently on that command line that in the IDE console [message #90854]

Tue, 28 April 2015 20:13

timothyja123
Messages: 57
Registered: February 2013

Member

When I run my build program from the command line resolve_all fails to find dependencies if they are in a sub directory. If I run it from the IDE's console everything works fine.

I've tried on both Linux and Windows and the results are the same. Can anyone explain this?

Thanks,
Tim

Report message to a moderator

Re: Resolve_all behaves differently on that command line that in the IDE console [message #90855 is a reply to message #90854]

Tue, 28 April 2015 20:19

timothyja123
Messages: 57
Registered: February 2013

Member

Wow I really messed up the heading.

Should be: "Resolve_all behaves differently on the command line than in the IDE console."

Report message to a moderator

Re: Resolve_all behaves differently on that command line that in the IDE console [message #90857 is a reply to message #90855]

Tue, 28 April 2015 21:24

Jim Pendleton
Messages: 165
Registered: November 2011

Senior Member

On Tuesday, April 28, 2015 at 9:19:26 PM UTC-6, timoth...@gmail.com wrote:
> Wow I really messed up the heading.
>
> Should be: "Resolve_all behaves differently on the command line than in the IDE console."

What's in !path when just before you run your script in both cases? What's your starting directory? The following should help you debug the situation.

IDL> print, !path
IDL> print, pref_get('IDL_PATH')
IDL> cd, current = c & print, c

Jim P.

Report message to a moderator

Re: Resolve_all behaves differently on that command line that in the IDE console [message #90858 is a reply to message #90857]

Tue, 28 April 2015 21:46

timothyja123
Messages: 57
Registered: February 2013

Member

On Wednesday, April 29, 2015 at 2:24:46 PM UTC+10, Jim P wrote:
> On Tuesday, April 28, 2015 at 9:19:26 PM UTC-6, timoth...@gmail.com wrote:
>> Wow I really messed up the heading.
>>
>> Should be: "Resolve_all behaves differently on the command line than in the IDE console."
>
> What's in !path when just before you run your script in both cases? What's your starting directory? The following should help you debug the situation.
>
> IDL> print, !path
> IDL> print, pref_get('IDL_PATH')
> IDL> cd, current = c & print, c
>
> Jim P.

Thanks Jim :)

Seems the IDE adds your project paths and subpaths to !path, adding the sub directory to !path in my build program fixed building from the command line.

Report message to a moderator

Re: Resolve_all behaves differently on that command line that in the IDE console [message #90861 is a reply to message #90858]

Wed, 29 April 2015 08:10

Jim Pendleton
Messages: 165
Registered: November 2011

Senior Member

When you create a new project in the IDL Workbench, there's a checkbox option "Update IDL path when project is opened or closed". By default, it's off.

If you'd turned that on when creating the project, that would explain the behavior you're seeing.

The IDL command line doesn't know about the organization of projects defined in the Workbench.

Jim P.

Report message to a moderator

Previous Topic:	Excessive Messages When Building Project
Next Topic:	Create folder below certain file

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 13:39:02 PDT 2025

Total time taken to generate the page: 0.00525 seconds