alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Petersen <jnsptrsn1@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: Takashi: please help (compiling alsa-driver)
Date: Fri, 15 Feb 2013 19:37:43 +0100	[thread overview]
Message-ID: <511E8077.4090900@gmail.com> (raw)
In-Reply-To: <s5hmwv8vh94.wl%tiwai@suse.de>

Am 13.02.2013 07:51, schrieb Takashi Iwai:
> At Tue, 12 Feb 2013 22:58:37 +0100,
> Jonas Petersen wrote:
>> How do you generate these snapshots?
> You need to have two git trees: sound.git tree containing the complete
> Linux kernel tree, and alsa-driver-build.git containing only the build
> stub for external builds.
>
> In the recent change, alsa-driver-build.git (or equivalent with
> alsa-driver.git in alsa-project.org) contains only README in master
> branch.  Checkout build branch instead.  Then you'll get the whole
> build stuff in alsa/ subdirectory.  Go into alsa subdirectory, then
> run
> 	ALSAKERNELDIR=../../sound ./gitcompile --with-debug=full --enable-dynamic-minors
>
> Alternatively, you can pull the alsa-driver-built git into kernel tree
> directly.  Then go to alsa subdirectory and run gitcompile.  In that
> case, you can omit passing "ALSAKERNELDIR=..." argument.

Thank you very much, that did help!

It didn't exactly answer my distinct question ("How do you generate 
these snapshots?"), but I was able to figure it out by myself now.

After some manual copying and linking and investigating I finally found 
what I need need to do:

$ ./utils/setup-alsa-kernel -c ../../sound

After that I can copy just the 'alsa' folder to another machine and it 
wil build.

The problem is, this procedure requires 1.6 GB of disk space. I'm 
building on another system that does not have that much space right now. 
The mentioned snapshot (and now the result from the 'setup-alsa-kernel' 
script) is consuming only about 100 MB after a full build.

These are all steps required:

~$ mkdir tiwai; cd tiwai
~/tiwai$ git clone git://github.com/tiwai/alsa-driver-build.git
~/tiwai$ git clone git://github.com/tiwai/sound.git
~/tiwai$ cd alsa-driver-build
~/tiwai/alsa-driver-build$ git checkout build
~/tiwai/alsa-driver-build$ cd alsa
~/tiwai/alsa-driver-build/alsa$ ./utils/setup-alsa-kernel -c ../../sound

Now the alsa folder contains everything needed.
Finally:

some-other-machine/alsa$ ./gitcompile --with-debug=full 
--enable-dynamic-minors

Regards
Jonas

      reply	other threads:[~2013-02-15 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 21:58 Takashi: please help (compiling alsa-driver) Jonas Petersen
2013-02-13  0:31 ` Raymond Yau
2013-02-13  6:53   ` Takashi Iwai
2013-02-14  3:20     ` Raymond Yau
2013-02-14  7:16       ` Takashi Iwai
2013-02-13  6:51 ` Takashi Iwai
2013-02-15 18:37   ` Jonas Petersen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=511E8077.4090900@gmail.com \
    --to=jnsptrsn1@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).