Skip to content

scancode does not start on windows exec #1129

@jeffmcaffer

Description

@jeffmcaffer

I exec'ing "c:\install\scancode-toolkit-2.9.2\scancode" from node fails looking for "c:\install\scancode-toolkit-2.9.2\bin\scancode" (note the "bin" segment. Seems that the bin folder is actually a symlink to Scripts. Using normal windows tools (i.e., drag and drop) to unzip the Release zip, you get a windows Junction for bin. That is fine in the UI and from the Command shell but when exec'ing from Node, it seems like the junction is not being followed (or is not available). I don't know enough about the internal workings of node and exec to know why this would be different.

Since the "Scripts" folder seems to include all the executable stuff, can it just called bin rather than using a symlink?

as a workaround right now I just deleted the bin link, and copied Scripts to bin. Not sure if there has to be something called Scripts. (i.e., could I have just renamed?)

@pombredanne FWIW, this is for ClearlyDefined.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions