Makefile: Ultimate SDK detection patch. The following works:

Makefile: Ultimate SDK detection patch. The following works:

# if SDK is in ../google_appengine
make serve
# if SDK is in PATH
make serve
# if SDK is ../appengine/sdk
SDK_PATH=../appengine/sdk make serve

[GvR, 2012-02-18 18:00:13]

By default the SDK installs in /usr/local/google_appengine, at least on Linux
and Mac. (This is where the Mac launcher puts/copies it, for example.)  Why not
include that path too?  (It's what I use. :-)

[techtonik, 2012-02-18 20:57:35]

I am not a Makefile guru, but I'll try if time permits.

It feels wrong that this file is not in Python. SCons/Fabric tool in standard
library would be awesome. =)

[gvrpython, 2012-02-18 21:28:16]

On Sat, Feb 18, 2012 at 12:57 PM,  <techtonik@gmail.com> wrote:
> I am not a Makefile guru, but I'll try if time permits.

Don't worry about it, it works for me even now, because
dev_appserver.py and appcfg.py are in my $PATH.

> It feels wrong that this file is not in Python. SCons/Fabric tool in
> standard library would be awesome. =)

Blame me. I like to use Make as an alternative for a bunch of tiny
shell scripts. Note that there is no actual "building" going on in
this Makefile; there are no real dependencies. My original idea was to
just use the Makefile as a shortcut for somewhat complex command
lines, so you don't have to remember all the necessary flags, and
invocations like "make deploy" or "make test" are somewhat uniform
across projects even if the implementations aren't.

Make is really overkill, except it is always installed and has a
pretty optimized command line, with a nice default and a nice way to
create aliases and groups of commands. Requiring SCons/Fabric would be
*really* overkill. Writing a Python script would be more work -- you'd
have to do a fair amount of command line parsing just to get started.
You could streamline this through a bunch of Bash aliases/functions
too, but I'm less familiar with those, and I like that it's localized
to the directory, always available when I'm in the directory, and
simple enough that if Make somehow isn't installed, you can still
figure out what to do just by reading the Makefile.

-- 
--Guido van Rossum (python.org/~guido)

[techtonik, 2013-06-15 16:08:06]

Here is the way to use Python from Makefile. All possible SDK paths are here.
PTAL.

[techtonik, 2013-06-17 15:44:18]

Simplified a lot. Please take a look.

[M-A Ruel, 2013-06-17 15:52:01]

On 2013/06/17 15:44:18, techtonik wrote:
> Simplified a lot. Please take a look.

Personally, lgtm

[techtonik, 2013-06-17 17:39:56]

Committed as a682007a3505. Thanks! ;)