-
Notifications
You must be signed in to change notification settings - Fork 29
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
Can't seem to get premake5 to create an sln file for the project #29
Comments
This repo still uses the old project generator, but it should work fine since I made it backwards compatible this time. Have you tried opening a command line in that folder and running |
well I managed to get the error this time but it doesn't really make much sense to me. C:\Users\cewei\Downloads\gmsv_serversecure-master (1)\gmsv_serversecure-master\projects>premake5 vs2019 and below is the lua code for the premake5.lua(I double checked the folderpath for garrysmod_common and it should be exactly as file explorer shows it) I also tried with the file path for garrysmod_common set to "../dependancies/garrysmod_common" aswell just to see if it worked. but that one simply errors out on line 8 saying I didn't provide a path to garrysmod_common
|
well I managed to get past the issue with premake5 by manually editing the lua files for it to automatically point to the path. tho now I'm unsure what to do with the new issue I have. I tried building it on release win32 with no edits made but I get this in my error console for vs https://pastebin.com/s6eV1K13 |
The path error is related to you editing the file directly and improperly. You're supposed to edit environment variables of your terminal/command line. |
So I've tried keeping the premake5 .exe and .lua files in the projects folder and moving it to the root folder. I've even edited the .lua file to point to the garrysmod_common folder(from your repo)
yet despite everything I try it simply doesn't build a sln. I simply get a split second where cmd pops up, but immediatly closes. I can't even get an error from it to know whats wrong with it since it closes immediatly
The text was updated successfully, but these errors were encountered: