-
Notifications
You must be signed in to change notification settings - Fork 0
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
Looks great! How do I start? #1
Comments
Answered my first question: To use |
Hey, thanks for checking it out!
Looks like you figured this out, but for everyone else (before I actually write some documentation for this): That's one way, but I would recommend putting this repository somewhere in your $PATH (if you're on something Unixy, not sure the equivalent for Windows). That way you can use it anywhere without copying it around all the time. Also, the main invocation is By default it will look for a rules.py in the current directory, or you can specify another path with All the outputs go in an
I was using it to convert some gigantic pile of makefiles generated by Eclipse into something reasonable (I was getting about a 10x reduction in size IIRC). I'm definitely curious to see if it can handle your makefiles, but it should probably be considered alpha/experimental. One limitation I know of is that right now it might change the order of command line arguments (though it handles flags that start with |
Judging from the syntax in the example, this looks wonderful. But how do I use it? Suppose I write a valid rules.py file. Is it just a matter of copying
make.py
to the same folder and then runpython3 make.py
?Also, do I need
gnu_make_parse.py
? Will it be useful for translating any of my giant unreadable GNU makefiles into this syntax?The text was updated successfully, but these errors were encountered: