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
makefile refers to "premake" executable instead of "premake4" #7
Comments
|
Yeah, valid concern. The problem is that I'm using 4.4-beta1 for bgfx which is not yet in any distro (on Linux you have to build from source). One way of fixing it is just creating premake symbolic link that points to premake4 (mklink or junction on windows). Also I was considering adding prebuilt premake for all platforms in bx/tools/bin, and some gnuwin tools for windows. Not sure if that's good idea? |
|
http://industriousone.com/premake/download provides pre-built binaries of premake4.4-beta4 for Linux. For me the exe always builds as premake4 if I'm building premake-stable from source. I'm actually trying to get premake 4 into Debian, although I'm packaging 4.3 for now. Anyway I just modified the makefile so that I can specify my premake exe, e.g.: PREMAKE := premake
all:
$(PREMAKE) --file=premake/premake4.lua vs2008the call make like so: make PREMAKE=premake4 As for adding pre-built tools, as it's only a couple I don't think it's a big deal downloading them personally, I just raised this bug as the exe name was not what I expected. Perhaps if you did want to bundle tools they could go in a different repo so they don't clutter the code repo? |
|
Fixed, it makes sense to change it to premake4 since that's what most of people will have it anyway. :) |
Updatebgfx leak layout
I tried following your build instructions however your makefile calls a "premake" executable. All of the downloads for premake-4.x have an executable named "premake4", the executable name was renamed between premake 3 and premake 4.
It might sound petty since people can just rename the exe, but I have my premake installed as a deb package so renaming isn't really ideal.
The text was updated successfully, but these errors were encountered: