Closed Salyourpal88 closed 1 year ago
I tried updating the Powershell version to 7.2.7.0 after reading some more discussions, but still no luck
I edit this file vcpkg/scripts/vcpkgTools.xml and downgrade the powershell to 7.2.6. I didn't get an error after but I got this:
Elapsed time to handle assimp:x86-windows: 3.079 min Total install time: 4.908 min assimp provides CMake targets:
# this is heuristically generated, and may not be correct
find_package(assimp CONFIG REQUIRED)
target_link_libraries(main PRIVATE assimp::assimp)
Can someone explains what that means? What must I do to make this right:
find_package(assimp CONFIG REQUIRED) target_link_libraries(main PRIVATE assimp::assimp)
because when I go to include the folder it isn't right
This is the usage provided by the port, you can use this in your CMake project to link and use the installed library. I tried it locally and it works fine, can you provide your simple CMake project?
I made my project a non-make and have no clue to how to adjust. I guess there is no more issues. I just need to figure that out. Thank you for your time.
Package: draco[core]:x86-windows -> 1.5.3
Host Environment
To Reproduce
vcpkg install assimp
Failure logs
C:\Users\salva\vcpkg\buildtrees\draco\copy-tool-dependencies-0-err.log
``` Fatal error. 0xC0000005 at System.Management.Automation.Security.SystemPolicy+WldpNativeMethods.WldpCanExecuteFile(System.Guid, WLDP_EXECUTION_EVALUATION_OPTIONS, IntPtr, System.String, WLDP_EXECUTION_POLICY ByRef) at System.Management.Automation.Security.SystemPolicy.GetFilePolicyEnforcement(System.String, System.IO.FileStream) at System.Management.Automation.ExternalScriptInfo.ReadScriptContents() at System.Management.Automation.Language.Parser.ParseFile(System.String, System.Management.Automation.Language.Token[] ByRef, System.Management.Automation.Language.ParseError[] ByRef) at Microsoft.PowerShell.ConsoleHost.DoRunspaceInitialization(Microsoft.PowerShell.RunspaceCreationEventArgs) at Microsoft.PowerShell.ConsoleHost.DoCreateRunspace(Microsoft.PowerShell.RunspaceCreationEventArgs) at Microsoft.PowerShell.ConsoleHost.CreateRunspace(Microsoft.PowerShell.RunspaceCreationEventArgs) at Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String, Boolean, System.Collections.ObjectModel.Collection`1Additional context
I tried updating the Powershell version to 7.2.6.0 thinking it would resolve the access violation, but sadly it didn't.