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

Fix native library detection - enables FAKE native library support #3593

Merged
merged 9 commits into from
Jun 11, 2019

Conversation

matthid
Copy link
Member

@matthid matthid commented Jun 8, 2019

Fixes two issues to enable fsprojects/FAKE#2007:

  • Allow Paket to detect native libraries in incorrectly packaged packages like system.data.sqlite.core
    -> We will emit a warning when we detect this.
  • We incorrectly reset the InstallModel when ONLY native libraries are in the package. This is wrong.
  • Fixed issue references in integration tests:
    • Renamed #3166 pack multitarget with p2p by tfm to #3558 pack multitarget with p2p by tfm
    • Renamed #3165 pack multitarget with p2p to #3317 pack multitarget with p2p

@@ -533,7 +539,7 @@ module InstallModel =

let removeIfCompletelyEmpty (this:InstallModel) =
let foldersEmpty =
isEmpty this.CompileRefFolders && isEmpty this.TargetsFileFolders && isEmpty this.RuntimeAssemblyFolders &&
isEmpty this.CompileRefFolders && isEmpty this.TargetsFileFolders && isEmpty this.RuntimeAssemblyFolders && isEmpty this.RuntimeLibFolders &&
Copy link
Member Author

Choose a reason for hiding this comment

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

It seems like this change (or the added trySscanf) or the added tests made it go over the 60minute appveyor limit. However, we need those bugfixes so I disabled some long running tests instead.

@forki can we merge this as is?

@matthid matthid changed the title Fix runtime libraries - enables FAKE native library support Fix native library detection - enables FAKE native library support Jun 9, 2019
@matthid
Copy link
Member Author

matthid commented Jun 9, 2019

@forki Somehow Build-Times went down again, not sure what happened. This is ready.

@matthid
Copy link
Member Author

matthid commented Jun 10, 2019

The CI failure is API rate limit. I guess I started too many builds :)

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

Successfully merging this pull request may close these issues.

2 participants