Closed sneak closed 13 years ago
variables in makefiles inherit from the environment and command line.
All of the following are ok:
PREFIX=${HOME}/local make install
make install PREFIX=${HOME}/local
etc. Both will set PREFIX in the Makefile, and will override any existing declarations.
I wonder if we should transition to an automake project? Thoughts @sneak?
Someone submitted a pull request for Tigger to homebrew: https://github.com/mxcl/homebrew/pull/6211 I think that the homebrew team wants us to make changes similar to what @sneak suggested. @sneak do you have the time/inclination to make tigger brew friendly? It would be sweet to get this on there. How does automake fit with the suggestions that they made?
Also @sneak I saw the makefile changes you wrote. Do you think those will address the brew issues?
Automake will do it and is the standard way in the OSS community for building projects in my opinion.
It's the normal:
./configure make make install
Chain automatically generated.
The only problem is I think it will take some time to setup (I've done it before).
Short-term might be best to do changes directly to the current makefile as @sneak suggests
Ok I tried to merge @sneak's changes from the fork queue but GitHub won't let me because they won't "apply cleanly." @Sneak do you mind if I take the gist of your changes, apply them on my machine and then push to git? Otherwise if you want to submit a pull request with them I will gladly merge. Let me know!
ah, probably because of changes to the makefile in the meantime (a few lines from me).
This just means you need to merge the files by hand to fix things.
This page might help: http://book.git-scm.com/3_basic_branching_and_merging.html
Right I was trying to do it from the fork-queue. Not sure how to merge a forked repo from the command-line though....
Never mind figured it out and pushed.
So would I do this with a parameter for the make install command?