Skip to content
This repository has been archived by the owner on Aug 2, 2020. It is now read-only.

Do we need stripCmdPath? #549

Open
snowleopard opened this issue Apr 3, 2018 · 3 comments
Open

Do we need stripCmdPath? #549

snowleopard opened this issue Apr 3, 2018 · 3 comments
Labels

Comments

@snowleopard
Copy link
Owner

snowleopard commented Apr 3, 2018

@izgzhen @angerman @alpmestan I've removed unused stripCmdPath:

-- ref: mk/config.mk
-- | Command line tool for stripping.
stripCmdPath :: Action FilePath
stripCmdPath = do
    targetPlatform <- setting TargetPlatform
    top <- topDirectory
    case targetPlatform of
        "x86_64-unknown-mingw32" ->
             return (top -/- "inplace/mingw/bin/strip.exe")
        "arm-unknown-linux" ->
             return ":" -- HACK: from the make-based system, see the ref above
        _ -> return "strip"

Is this the right thing to do? There is the following comment in Settings.Builders.GhcCabal:

-- don't strip libraries when cross compiling.
-- XXX we need to set --with-strip= (stripCmdPath :: Action FilePath), and if it's ':' disable
--     stripping as well. As it is now, I believe we might have issues with stripping on
--     windows, as I can't see a consumer of `stripCmdPath`.
@izgzhen
Copy link
Collaborator

izgzhen commented Apr 3, 2018

stripCmdPath was previously used in install by GhcCabal (copy subcommand).

@izgzhen
Copy link
Collaborator

izgzhen commented Apr 3, 2018

I suggest let's keep this issue open and delete the dead code for now

@snowleopard
Copy link
Owner Author

@izgzhen Thanks, agreed!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants