Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

msbuild: init at 16.3 #66134

Closed
wants to merge 3 commits into from
Closed

msbuild: init at 16.3 #66134

wants to merge 3 commits into from

Conversation

jirkadanek
Copy link
Member

@jirkadanek jirkadanek commented Aug 5, 2019

Motivation for this change

Based upon #43680 and #50842
(Sort of) fixes #29817
Depends on PRs #65875 and #66131

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @thoughtpolice @obadz @vrthra @worldofpeace @samueldr

@jirkadanek
Copy link
Member Author

I guess I did all I could at this point. I can build and run msbuild on my machine.

Known issues: My checkPhase does not seem to be running, I am skipping tests during build, and I am getting a failure from the ci bot which I don't understand.

@jirkadanek jirkadanek changed the title [WIP]msbuild: Init at 16.3 msbuild: Init at 16.3 Aug 6, 2019
@worldofpeace
Copy link
Contributor

Have you tried doCheck = true @jdanekrh?

@jirkadanek jirkadanek changed the title msbuild: Init at 16.3 msbuild: init at 16.3 Aug 6, 2019
@jirkadanek
Copy link
Member Author

Rebased and ready for review. Only outstanding work to do is the disabled unit tests during build. Can I get it in without them? I have installCheckPhase, at least.

@jirkadanek
Copy link
Member Author

One more issue. Jetbrains.rider does not accept the wrapped executable, it only takes the dll. But then the MSBuildExtensionsPath variable is not configured and builds fail. I can fix that in the rider gui by setting msbuild global property, but it is a hassle.

@jirkadanek jirkadanek mentioned this pull request Aug 6, 2019
9 tasks
@jirkadanek
Copy link
Member Author

Still one more MSBuildExtensionsPath thing. OmniSharp autoconfiguration does not pick it correctly either, see #43680 (comment).

@Mic92
Copy link
Member

Mic92 commented Aug 7, 2019

@jdanekrh maybe you can have an unwrapped version that is passed to rider and then you set MSBuildExtensionsPath in rider itself.

@jirkadanek
Copy link
Member Author

jirkadanek commented Aug 7, 2019

@Mic92 The wrapper must be a shell script, though, right? I cannot wrap a .net dll in another dll.

My problem is that Rider needs to be given a MSBuild.dll, if I give it a shell script, it screams

Cannot open assembly '/nix/store/sn4h4a3qbp11yng2621yqzk16blvn6bw-msbuild-16.3+xamarinxplat.2019.07.26.14.57/bin/msbuild': File does not contain a valid CIL image.

@jirkadanek
Copy link
Member Author

Sorry, I misunderstood the comment. Yes, you are absolutely right. What you said is what I am doing to make this work for me.

};

in [
(fetchNuGet {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this generated?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jirkadanek
Copy link
Member Author

This was merged as part of PR #66299 in commit a9b4e75

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

Successfully merging this pull request may close these issues.

mono50 doesn't include msbuild
5 participants