From: "haoshun" <haoshun@amoi.com.cn>
To: alsa-devel <alsa-devel@alsa-project.org>
Subject: Problems in writing test apps
Date: Thu, 3 Apr 2008 16:59:33 +0800 [thread overview]
Message-ID: <200804031659332034329@amoi.com.cn> (raw)
Hi:
sorry,forget to add the subject right now...
I'm confused by a problem when i modify a test application "alsa-lib-1.0.13/test/control.c".
I wanna use the structure "snd_ctl_elem_value_t",but when i write like this:
snd_ctl_elem_value_t aaa;
there will be an error:
storage size of 'aaa' isn't known
while
snd_ctl_elem_value_t *aaa;
makes no errors. But i can't change it directly such as:
aaa->id=test_id ; //test_id is defined before
cause it will bring an error:
dereferencing pointer to incomplete type
I think i should use the function like "snd_ctl_elem_info_set_id",but i just want to know why,i don't think it disobeys the C syntax.Is there something different in the ALSA making procedure?or Makefile?
haoshun
2008-04-03
next reply other threads:[~2008-04-03 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 8:59 haoshun [this message]
2008-04-03 9:59 ` Problems in writing test apps Matthias Koenig
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=200804031659332034329@amoi.com.cn \
--to=haoshun@amoi.com.cn \
--cc=alsa-devel@alsa-project.org \
/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