Skip to content

Clean up build dependencies #1234

Description

Activity

  1. andyleejordan commented on Jun 29, 2016

    @andyleejordan
    MemberAuthor

    sergei (@vors) we talked about this briefly a week or two ago; what else was there?

  2. andyleejordan commented on Jun 29, 2016

    @andyleejordan
    MemberAuthor

    We are going to need a properly built SMA reference library. It's blocking the PSReadLine export as well.

    /cc Jason Shirk (@lzybkr)

  3. lzybkr commented on Jun 29, 2016

    @lzybkr
    Contributor

    James Truher (@JamesWTruher) built the reference assemblies for full that we publish to NuGet - hopefully we can reuse some of that process for PowerShell Core.

  4. andyleejordan commented on Jul 15, 2016

    @andyleejordan
    MemberAuthor

    For the rename from LINUX to UNIX, while not everyone is happy with the choice (some preferring NIX), I'll posit that .NET Core has been using "Unix" to mean Linux/OS X/FreeBSD etc., and so it would be more than reasonable to follow their example.

  5. andyleejordan commented on Jul 18, 2016

    @andyleejordan
    MemberAuthor

    I tested out the various dotnet options (optimize, debugType, etc.) and the only that made any real difference (on Windows) was compiling in Debug or Release configurations, where the latter was about 30% faster with Get-Command.

    For reference, this is how dotnet is passing options to Roslyn, and this is what they mean.

  6. andyleejordan commented on Jul 18, 2016

    @andyleejordan
    MemberAuthor

    I've also verified that the Linux configuration does not define DEBUG (we don't do it explicitly, and nothing is implicitly doing so), thus assertions are not performed, making every Linux build equivalent to a Release configuration on Windows.

  7. andyleejordan commented on Jul 18, 2016

    @andyleejordan
    MemberAuthor

    For what it's worth, the default Release configuration created by dotnet does enable optimizations.

  8. andyleejordan commented on Oct 4, 2016

    @andyleejordan
    MemberAuthor

    This was a meta issue that is no longer required, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Issue-Metaan issue used to track multiple issuesWG-Maintainers-Buildspecific to affecting the build

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions