On Sun, Apr 5, 2009 at 6:36 PM, Al Sutton <a...@funkyandroid.com> wrote:

>
> I tried the instructions from the git repo for building windows and they
> don't work.
>
> To start  with cygwin bases everything off /cygwin rather than / so even
> trying to run repo gets;
>
> /bin/sh: bad interpreter: No such file or directory
>

Normally, cygwin also mounts / as a short-cut to your cygwin installation so
you
should be able to run /bin/sh directly. Note that I said "normally", because
there are
unfortunately quite a few ways to get a Cygwin install on a Windows PC, each
one
of them which its own can of worms.

I suggest starting from scratch with the "usual" way, i.e.:

- uninstall *anything* vaguely related to Cygwin on your machine
- go to http://www.cygwin.com and download the "setup.exe" program
- run setup.exe and ensure that:

   = You install on a NTFS partition
   = All directories in the installation path fit the 8.3 DOS convention
(right)
   = Choose "Unix line ending" when asked by the installation dialog
   = Don't try to much with the default mount paths (i.e. it's possible to
get rid of the /cygdrive/<drive> stuff with some tweaking, but this makes
some tools miserable).

In addition, I really recommend the following:

install python and wget by default, then later install "cyg-apt" from
http://www.lilypond.org/~janneke/software/cyg-apt
this tool will allow you to download and install additionnal packages from
the command-line without using the brain-dead setup.exe GUI
(NOTE: you may need to update the script to use a better mirror than the
default. Look at the lines that read "mirror = ....")

use puttycyg as the terminal (http://code.google.com/p/puttycyg/), or even
Terminator (http://software.jessies.org/terminator/) as they are far better
than the default Windows console or rxvt.

If you need MSys, do not install it in the same location that Cygwin if
possible, this really messes things sometimes.

Hope this helps


> And if you hack around that by altering repo to point to /cygwin/bin/sh you
> get;
>
> Getting repo ...
>   from git://android.git.kernel.org/tools/repo.git
> warning: templates not found /usr/share/git-core/templates/
> remote: Counting objects: 386, done.
> remote: Compressing objects: 100% (234/234), done.
> git: 'index-pack' is not a git-command. See 'git --help'.
> fatal: write error (Broken pipe)
> fatal: index-pack failed
>
> :(
>
> Al.
>
>
> ---
>
> * Written an Android App? - List it at http://andappstore.com/ *
>
> ======
> Funky Android Limited is registered in England & Wales with the
> company number  6741909. The registered head office is Kemp House,
> 152-160 City Road, London,  EC1V 2NX, UK.
>
> The views expressed in this email are those of the author and not
> necessarily those of Funky Android Limited, it's associates, or it's
> subsidiaries.
>
>
> -----Original Message-----
> From: android-developers@googlegroups.com
> [mailto:android-develop...@googlegroups.com] On Behalf Of Jean-Baptiste
> Queru
> Sent: 05 April 2009 14:12
> To: android-developers@googlegroups.com
> Subject: [android-developers] Re: Cupcake SDKs available for download
>
>
> -I'd like to point out that this isn't an official SDK, with e.g. no
> guarantee that applications developed with it will work on future versions
> of Android. Should anyone have questions about using it, please use the
> android-discuss group as android-developers is for questions about the
> official SDKs, and be sure to mention which specific version of Al's SDK
> you're using.
>
> -Al, you might be looking for this:
>
> http://android.git.kernel.org/?p=platform/development.git;a=blob;f=docs/howt
> o_build_SDK.txt<http://android.git.kernel.org/?p=platform/development.git;a=blob;f=docs/howt%0Ao_build_SDK.txt>
> ;h=4b6507d4a0bf0dfaed5e1660b858caf641e8eccd;hb=b3fb2a6ef1df35
> 34dee5b1d09ab72d129d3697c7#l92
>
> -How about distributing it with BitTorrent? This seems like a perfect use
> case.
>
> JBQ
>
> On Sun, Apr 5, 2009 at 12:42 AM, Al Sutton <a...@funkyandroid.com> wrote:
> >
> > I've compiled up the Linux & Mac OS X Intel SDKs from the public git
> > repository and have put them up for download (If anyone can get
> > instructions on building a Windows SDK I will do what I can to create
> > a Windows SDK as well).
> >
> > *PLEASE NOTE* In order to ensure that I don't end up with a massive
> > bandwidth bill you will need to log into AndAppStore to download the
> > SDKs, and, if things get silly, download limits may be introduced.
> >
> > You are, of course, free to pass on the SDK to as many people as you
> > want after you've downloaded, but please do not pass around links to
> > direct downloads without logins at AndAppStore because I'd like to
> > continue to update them but if a bandwidth cost issue comes up then I
> won't.
> >
> > Anyway, once you've logged into AndAppStore the link to the Cupcake
> > SDKs is in the Developers Area menu on the right of the page.
> >
> >
> > Al.
> >
> > ---
> >
> > * Written an Android App? - List it at http://andappstore.com/ *
> >
> > ======
> > Funky Android Limited is registered in England & Wales with the
> > company number  6741909. The registered head office is Kemp House,
> > 152-160 City Road, London,  EC1V 2NX, UK.
> >
> > The views expressed in this email are those of the author and not
> > necessarily those of Funky Android Limited, it's associates, or it's
> > subsidiaries.
> >
> >
> >
> > >
> >
>
>
>
> --
> Jean-Baptiste M. "JBQ" Queru
> Android Engineer, Google.
>
> Questions sent directly to me that have no reason for being private will
> likely get ignored or forwarded to a public forum with no further warning.
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to