-
-
Notifications
You must be signed in to change notification settings - Fork 376
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
RedistCopy.OnPostprocessBuild fails writing to Steamworks.NET.txt on Linux #350
Comments
Indeed, that seems to be the case.
Could you try grabbing the latest from the github master branch? Going to put out a new release with it this week. IIRC there was some change to the Steamworks.NET.txt creation which may have been fixed since September. |
Seeing the same thing on 2019.3.13f on Linux only (Windows and macOS build fine). I see the commit 9e168df that fixes the previous report of this at #278, so I grabbed that file only and will get the proper release later. The building process seems to work, although I also can't verify for sure right now as I need to set up a VM for that. |
I was having this issue on Win 10 2019.3.13f1, but updating to the latest has fixed it. |
I created a fix for this but you need to change the file yourself until a fix is implemented.
This works for me because the Plugins folder was never being created. This line ensures that the directory exists, and if it already exists, nothing happens. It doesn't mess up my windows or mac builds either! Let me know if this works! |
Thanks @Gelberdaniel19 I applied that in 354bb21 |
Hey there!
I get the following error every time I try to make a linux build on my mac:
Going to that location, I can indeed see that that file doesn't exist. I don't have access to a Linux computer right now so haven't figured out whether the Steam integration also actually works on Linux builds of the game, but regardless it's probably good to look into this. I'm assuming because of recent changes to how Unity handles plugins that this .txt isn't copied into the plugins folder?
I'm on Unity 2019.3.10, compiling from 10.15.4, using the latest september release for this plugin.
The text was updated successfully, but these errors were encountered: