Invalid path breaks Linux build when adding Facil package
See original GitHub issueAfter adding Facil to a new net5.0 console application on Linux, dotnet build
fails, because the Facil.Generator.dll can not be found.
After manual checking I can confirm, that the search path seems correct, but the FacilGenerate.targets file contains an invalid path separator. Changing the file manually allows the build to succeed.
I’ve not tested on Windows, but I assume, using a slash “/” instead of backslash “\” will work there too. So I suggest replacing the backslash in Facil.Package/FacilGenerate.targets with a slash (like already used in Facil.Generator/FacilGenerate.targets).
Thank you very much.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
(make) Recipes breaks after definding PATH - linux
I am trying to automate the building of my toolchain, however every time I set my PATH using a recipe, it breaks the...
Read more >build error message for invalid pkg path · Issue #2177 · r-lib ...
Error: path must exist. This causes some user-confusion because there is a separate, unrelated path option for devtools::build that is passed to ...
Read more >Troubleshoot pipeline runs - Azure DevOps
Learn how to troubleshoot pipeline runs in Azure Pipelines and Team Foundation Server.
Read more >11 Ways to Fix "The System Cannot Find The Path ...
4. Verify the File's Path ... If you've been getting this error message on the Command Prompt, check whether you're typing the correct...
Read more >Bash Reference Manual
This chapter briefly summarizes the shell's 'building blocks': commands, control structures, shell functions, shell parameters, shell expansions ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
v1.3.1 is in the pipeline now and will be published shortly.
Thank you for a short and concise problem description and solution suggestion. That made it a lot easier to fix this in a timely manner!
Seems it works fine on Windows. I have pushed the fix to
master
. Are you able to try it out before I publish it? Just build and pack the Facil.Package project (preferably in two separate steps, to work around somedotnet
bugs), and you’ll get a nuget in the nupkg folder in the repo root. You can consume that in a project using a local package source as shown here. Note that if you don’t useglobalPackagesFolder
as shown, you have to delete the cached “unpacked” Facil version you likely have in your local NuGet cache (~/.nuget
I suppose).The target files in Facil.Package were old and unused; I didn’t know they were still around. I have deleted them now.