Build and release pipeline broken? #12
Comments
|
Yea there was a bug in the build script I used, Thanks for pointing it out. I fixed it and just released a new version with some improvements. |
|
The Mac build is still very broken. Not sure what's going on. The archive contains MS DLLs, and file names have paths in them. |
|
Its an issue with the Powershell module I used to compress the archive. It looks fine on any windows machine but Mac and Linux don't like the way it compresses it. I uploaded new files, let me know how it looks don't have a mac to compare with. |
|
Well - you don't need a mac to open zips, right? ;) The Zips in BETA2 are still containing a lot of stuff not needed, I think. Just an excerpt: |
|
That is the default output of the dotnet build process for Mac. Some of those dll's are probably not needed, but given that I don't have a Mac to test with I don't want to start removing dll's. I could use Trim, but in the past I have had issues with it and again without being able to test don't want to risk it. I did resolve an issue where zip files on Mac and Linux would convert folders to filenames that is an issue with PowerShell and how it creates Zip files. Which is resolved, but as far as the dll's go they aren't hurting anything, just create a shortcut to launch it and forget they are they. If I get a reliable way to test the Mac release myself I will look into trimming the unneeded dlls, if there are any. This program is written in C# so even if the dll says Microsoft or Windows it might still be needed to run on Mac there might be some dependency on it in either a package I use or the dotnet library. |
|
Ah ok, my bad. Just installed VS Code and the dotnet - maybe there is something I can contribute. ;) |
Would love to try out this project but it seems that the Mac archive contains a windows exe and the windows version contains a mac zip file that contains the zip file again.
Can we have a new release? many thanks
The text was updated successfully, but these errors were encountered: