in reply to How let Inline tell space in path?

You can get around that immediate problem by copying the _Inline/config file from another location into the C:\Documents and Settings\_Inline folder - ie run an Inline::C script in (say) C:\nospaces, then copy C:\nospaces\_Inline\config across to the C:\Documents and Settings\_Inline folder.

But, with gcc at least, that only defers the problem. You'll get to the stage where gcc -c  -IC:/Documents and Settings ... gets run - but it needs to be run as something like gcc -c  "-IC:/Documents and Settings" ....
To fix that problem you need to hack at C.pm. There's a patch at http://rt.cpan.org/Public/Bug/Display.html?id=4150 which you might find useful. I think (not sure) Eric Wilhelm has a build of Inline (google for Inline-0.44_01) that does permit the running of scripts inside directories with spaces.

For mine, the best solution is to not run Inline scripts in paths with spaces. In fact, one would be best advised to *never* enter such locations under any circumstances whatsoever.

Cheers,
Rob

Replies are listed 'Best First'.
Re^2: How let Inline tell space in path? (system)
by tye (Sage) on Oct 24, 2007 at 05:51 UTC

    Which highlights how system needs to be fixed on Win32 so that 

    my $cc= 'c:/opensource tools/gcc/gcc.exe';
my $flag= "-lIcorice";
my $file= 'c:/dockets and filings/case.c';
system( $cc, $flag, $file );

    [download]

    puts the needed quotes around the first and third "arguments" when constructing the command line to be used. Well, at least it highlights that to me.

    - tye        

[reply]
[d/l]
Re^2: How let Inline tell space in path?
by diotalevi (Canon) on Oct 25, 2007 at 02:49 UTC

    *shrug* It's Inline. It's built on assumptions. That there's no spaces is just another unreasonable one.

    ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

[reply]
      *shrug* It's Inline. It's built on assumptions. That there's no spaces is just another unreasonable one

      Both nmake and dmake are built on the same assumption. I therefore (personally) don't see any reason that Inline should do otherwise.

      Cheers,
      Rob
[reply]

        That doesn't make either nmake or dmake reasonable. I've been able to use spaces and other meaningful punctuation in my paths for decades now. It's the tool's problem if it can't cope. Well... the tool makes it *my* problem but then it's just a bad tool.

        ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

[reply]

In Section Seekers of Perl Wisdom