help-gengetopt
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [help-gengetopt] "free_string_field" defined but not used


From: Lorenzo Bettini
Subject: Re: [help-gengetopt] "free_string_field" defined but not used
Date: Mon, 06 Sep 2010 12:34:07 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4

This issue is fixed in the current git version (and in the next release).

Please let me know whether you have problems accessing the sources using git, and whether you need a tarbal.

cheers
        Lorenzo

On 03/03/2010 07:22 PM, Andre Noll wrote:
Hi Lorenzo, list

I'm getting this gcc warning when compiling sources the generated by
gengetopt-2.22.4. Looking at the generated .c file, it appears that
gengetopt generates the static free_string_field() function but never
ends up using it.

Of course I could compile the .c Files generated by gengetopt without
using -Wall to get rid of the message, but I think it would be cleaner
if unused static functions would not be generated at all.

The corresponding .ggo File contains only a single flag option,
and I'm using the following command line:

gengetopt --set-version="(paraslash git, associative expansion)" \
                 --output-dir=cmdline \
                 --set-package=mp3dec_filter \
                 --arg-struct-name=mp3dec_filter_args_info \
                 --file-name=mp3dec_filter.cmdline \
                 --func-name=mp3dec_cmdline_parser

Any hints on how to avoid that warning?

Thanks
Andre


--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
ICQ# lbetto, 16080134     (GNU/Linux User # 158233)
HOME: http://www.lorenzobettini.it MUSIC: http://www.purplesucker.com
http://www.myspace.com/supertrouperabba
BLOGS: http://tronprog.blogspot.com  http://longlivemusic.blogspot.com
http://www.gnu.org/software/src-highlite
http://www.gnu.org/software/gengetopt
http://www.gnu.org/software/gengen http://doublecpp.sourceforge.net



reply via email to

[Prev in Thread] Current Thread [Next in Thread]