Create a new dylib project

[caizixian]

Can I use cargo new <name> --dylib
Currently, I can only cargo new <name> and then edit the Cargo.toml manually.

[alexcrichton]

The current method of creating a dylib isn't exactly the most desirable, and I've long wanted to tweak it to work a bit better with the rest of the system. That being said this would probably be fine to add for now as we'll probably continue supporting it later.

[stale]

As there hasn't been any activity here in a while would someone (the author, a team member, or any interested party) be able to summarise the current state, perhaps making explicit:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[caizixian]

I believe that --dylib option is still not supported.

Attached is the output

cargo new --help
cargo-new
Create a new cargo package at <path>

USAGE:
    cargo new [OPTIONS] <path>

OPTIONS:
        --vcs <VCS>       Initialize a new repository for the given version control system (git, hg, pijul, or fossil)
                          or do not initialize any version control at all (none), overriding a global configuration.
                          [possible values: git, hg, pijul, fossil, none]
        --bin             Use a binary (application) template [default]
        --lib             Use a library template
        --name <NAME>     Set the resulting package name, defaults to the directory name
    -v, --verbose         Use verbose output (-vv very verbose/build.rs output)
    -q, --quiet           No output printed to stdout
        --color <WHEN>    Coloring: auto, always, never
        --frozen          Require Cargo.lock and cache are up to date
        --locked          Require Cargo.lock is up to date
    -Z <FLAG>...          Unstable (nightly-only) flags to Cargo, see 'cargo -Z help' for details
    -h, --help            Prints help information

ARGS:
    <path>

cargo --version
cargo 1.29.0 (524a578d7 2018-08-05)

[epage]

I'm proposing we close this.

I feel like dylib's aren't a large enough use case for built-in support but that we should instead close in favor of #5151.

[weihanglo]

Agree. Closing in favor of #5151.