| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@paulie4 I don't see the same issue in latest VS 2017 Enterprise (15.8.5) . But still we need to transition from unmanaged exports to a friendly fork dllexport: It builds fine using setup.py too. |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## master #759 +/- ##
==========================================
+ Coverage 77% 77.06% +0.05%
==========================================
Files 63 63
Lines 5741 5777 +36
Branches 907 907
==========================================
+ Hits 4421 4452 +31
- Misses 1021 1026 +5
Partials 299 299
Continue to review full report at Codecov.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
…ment, see #609, #720, and #609 (comment)
What does this implement/fix? Explain your changes.
iterop37.cs was missing from Python.Runtime.csproj
Does this close any currently open issues?
no, #609 and #720 were already closed, although, I don't know how #720 closed without this change...
Any other comments?
NOTE: to be able to build a usable clr.pyd using Visual Studio 2017, we had to run the following:
This is because we got the following error message in the build's output (even though the project looks like it built correctly), i.e. since the UnmanagedExports package seems to be looking for lib.exe in the wrong place for VS2017, we put the files where it was expecting to find them: