Nabble - Gnu - Gengetopt

Re: Some minor issues with 2.22.3

2009-11-16T02:08:54Z

Debarshi Ray wrote:
> The test_manual_help_cmd.ggo and test_manual_help.c files mentioned in
> doc/README.example are missing; and most of the source files have
> their executable bit wrongly set.
>
> Cheers,
> Debarshi

thanks I'll address these issues.

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Some minor issues with 2.22.3

2009-11-11T21:16:30Z

The test_manual_help_cmd.ggo and test_manual_help.c files mentioned in
doc/README.example are missing; and most of the source files have
their executable bit wrongly set.

Cheers,
Debarshi
--
One reason that life is complex is that it has a real part and an
imaginary part.
-- Andrew Koenig

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

gengetopt and g++4.4.1 constness error

2009-10-21T08:20:06Z

I have updgraded my box, and have now gcc 4.4.1 as default.

when compiling the .c/.h generated by gengetopt (gengetopt-2.22.3 as pakaged by mandriva) , i have theses errors compiling internal gengetopt function with g++ :

cglCmdLine.c: In function ‘char* get_multiple_arg_token(const char*)’:
cglCmdLine.c:354: erreur: invalid conversion from ‘const char*’ to ‘char*’
cglCmdLine.c: In function ‘char* get_multiple_arg_token_next(const char*)’:
cglCmdLine.c:404: erreur: invalid conversion from ‘const char*’ to ‘char*’

with previous g++ 4.3.1 version, it was compiling without a warning.

if i compile with gcc (not g++), it works, but, since it's a c++ project, i need to put a specific rule in my makefile to compile gengetopt generated files.

Alexandre

From forum: Gnu - Gengetopt - Help

GNU Gengetopt 2.22.3

2009-10-01T01:02:24Z

GNU Gengetopt 2.22.3 has been released. It is available from
ftp://ftp.gnu.org/gnu/gengetopt/ and mirrors of that site (see list of
mirror sites at http://www.gnu.org/order/ftp.html).

GNU Gengetopt generates a C function that uses getopt_long function
to parse the command line options, validate them and fill a
struct.

Version 2.22.3

* enum option values can contain + and - (thanks to Papp Gyozo).
* fixed compilation problems due to macro FIX_UNUSED which was not
in the right place (thanks to Matthew Junker)
* --header-output-dir and --src_output-dir to store cmdline.h
separately from cmdline.c (thanks to Yegor Yefremov)
* #include <getopt.h> in the generated files, instead of "getopt.h"
* generated functions use prototypes with char ** instead of
char *const *

You can also find details about new features on my blog, in this area:
http://tronprog.blogspot.com/search/label/gengetopt.

Visit the Gengetopt home page at
http://www.gnu.org/software/gengetopt

Anonymous CVS access is available. Please visit
http://savannah.gnu.org/projects/gengetopt/
where you can find detailed descriptions of how to access the CVS
(read-only). Release-candidate versions are available
through CVS.

Bug reports should go to bug-gengetopt@....

The following mailing lists are available:

* help-gengetopt@..., for generic discussions about the program
and for asking for help about it (open mailing list),
http://mail.gnu.org/mailman/listinfo/help-gengetopt
* info-gengetopt@... , for receiving information about new
releases and features (read-only mailing list),
http://mail.gnu.org/mailman/listinfo/info-gengetopt

if you want to subscribe to a mailing list just go to the URL and follow
the instructions or just send me an e-mail.

cheers
Lorenzo

--
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

_______________________________________________
Info-gengetopt mailing list
Info-gengetopt@...
http://lists.gnu.org/mailman/listinfo/info-gengetopt

From forum: Gnu - Gengetopt - Announce

Re: [feature-request] different output folders for .h and .c and dummy conf file

2009-09-28T01:21:23Z

>> I've made a quick patch to enable different output folders for *.h and
>> *.c files. Could you review it?
>>
>>
>> Add --header-output-dir and --src_output-dir to store cmdline.h
>> separately from cmdline.c
>>
>
> Hi Yegor
>
> your patch is in the CVS right now, and it works like a charm :-)
>
> I've also added some tests.
>
> If you update, remember to run autoreconf

I've updated the source tree. Everything is working. Thank you for including this feature.

Regards,
Yegor

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: [feature-request] different output folders for .h and .c and dummy conf file

2009-09-27T09:33:26Z

Yegor Yefremov wrote:
> Hi Lorenzo,
>
> I've made a quick patch to enable different output folders for *.h and *.c files. Could you review it?
>
>
> Add --header-output-dir and --src_output-dir to store cmdline.h separately from cmdline.c
>

Hi Yegor

your patch is in the CVS right now, and it works like a charm :-)

I've also added some tests.

If you update, remember to run autoreconf

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-18T02:02:55Z

>> Do you have any solution on how to format examples so that they look
>> correct in both gengetopt help and man page? I'd like to have it in
>> the following form:
>>
>> 1. if example and its description are short enough they should be
>> placed on the same line with a tab between them
>> 2. if example and its description are longer then place the
>> description below and make some indentation as for the options.
>
> Yegor, I tried with this reduced .ggo file (I modified it):
>
> # Name of your program
> package "hwtest" # don't use package if you're using automake
> # Version of your program
> version "1.2.1" # don't use version if you're using automake
>
> args "--conf-parser"
>
> # Options
> section "Common options"
> sectiondesc="this options are common to all test modules"
> text ""
> option "cfg" - "Configuration file" string typestr="filename"
> optional
> option "cycles" - "Number of test cycles" int default="0" optional
> text "\n"
> text "Examples:\n\n"
>
> text "hwtest --cycles=1 --size=4096 --net --verbose\n\n"
> text "execute network test with 4096 byte big test file in verbose mode\n"
> text "\n"
>
> text "hwtest --cycles=1 --mpci\n"
> text "execute MiniPCI test\n"
> text "\n"
>
> and the first line of help is formatted correctly by help2man, since it
> contains a double \n (while the second one is not, since it contains
> only one \n):
>
> EXAMPLES
> hwtest --cycles=1 --size=4096 --net --verbose
>
> execute network test with 4096 byte big test file in verbose mode
>
> hwtest --cycles=1 --mpci execute MiniPCI test
>
> so it's just a matter of formatting the examples text as help2man
> expects, I guess...
>
> or am I missing something?

Thank you for this example. I'll follow your advice and add extra \n for now. But what I wanted to say was, I'd like examples to be handled as options. Like this:

section "Examples" (perhaps without sectiondesc)
example "example string" - "examples description"

and the formatting should also be the same as for the options. What do you think about it?

Regards,
Yegor

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: gengetopt with native Win32 CL.EXE

2009-09-17T11:42:21Z

Andreas Baumann wrote:

> On Thu, Sep 17, 2009 at 12:03:18PM +0200, Lorenzo Bettini wrote:
>
>> Andreas Baumann wrote:
>>
>>> Hi,
>>>
>>>
>>> I tried to produce the C and header files from a GGO file for native
>>> Windows compilation with CL.EXE. Using any of the Cygwin or MinGW ports
>>> of 'gengen` and 'gengetopt` as built-chain works.
>>>
>>> As I see it, there is a small problem in the generated C code with the
>>> FIX_UNUSED macro which is sometimes called before or in the middle of a
>>> variable declaration in generated functions.
>>>
>>> After patching with gengetopt-2.22.2-fix-unused.patch, compilation is no problem.
>>>
>>>
>> Hi Andreas
>>
>> actually this should have already been fixed by this candidate
>> release, if you want to try it
>>
>> http://gdn.dsi.unifi.it/~bettini/gengetopt-2.22.3.tar.gz
>>
>
> Ah, perfect. :-)
>
> Yes, the patch corrects exactly the same lines as in 2.22.3.
> Works fine.
>
>

happy to hear that!
I'll release that version soon

cheers
Lorenzo

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: gengetopt with native Win32 CL.EXE

2009-09-17T10:54:39Z

On Thu, Sep 17, 2009 at 12:03:18PM +0200, Lorenzo Bettini wrote:

> Andreas Baumann wrote:
> >Hi,
> >
> >
> >I tried to produce the C and header files from a GGO file for native
> >Windows compilation with CL.EXE. Using any of the Cygwin or MinGW ports
> >of 'gengen` and 'gengetopt` as built-chain works.
> >
> >As I see it, there is a small problem in the generated C code with the
> >FIX_UNUSED macro which is sometimes called before or in the middle of a
> >variable declaration in generated functions.
> >
> >After patching with gengetopt-2.22.2-fix-unused.patch, compilation is no problem.
> >
>
> Hi Andreas
>
> actually this should have already been fixed by this candidate
> release, if you want to try it
>
> http://gdn.dsi.unifi.it/~bettini/gengetopt-2.22.3.tar.gz

Ah, perfect. :-)

Yes, the patch corrects exactly the same lines as in 2.22.3.
Works fine.

Thanks

Andreas

> hope to hear from you soon
> cheers
> Lorenzo
>
> --
> 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
>
>
> _______________________________________________
> Help-gengetopt mailing list
> Help-gengetopt@...
> http://lists.gnu.org/mailman/listinfo/help-gengetopt

--
Andreas Baumann
Trottenstrasse 20
CH-8037 Zuerich
Telefon: +41(0)76/373 01 29
E-mail: abaumann@...
Homepage: www.andreasbaumann.cc

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: accept option arguments (even in enum)

2009-09-17T10:29:43Z

Gyozo, on august I sent this email with a version that should implement
what you requested, have you managed to try it?

hi

I've uploaded a candidate release here

http://rap.dsi.unifi.it/~bettini/gengetopt-2.22.3.tar.gz

which provides this feature (you may want to take a look at test_values*
files).

look forward to getting some feedback and then I'll release it :-)

cheers
Lorenzo

Papp Gyozo (VBuster) wrote:

> Hi,
>
>>> What do you think? gengetopt should enable symbols in enums or should we
>> rephrase our idea? Please note that this option is multiple enum, so the
>> real strength of this approach that custom mixed filter definitions can be
>> described this way:
>>> --filter=+other,-missing
>> well I think this would be feasible without any problem!
>> My only concern is the literals used for the actual C enum values: + and
>> - are not valid characters, so these characters should be translated
>> in the C enum...
>>
>> something like
>>
>> enum { filter_MINUS_UNSPECIFIED, filter_PLUS_OK, ... }
>>
>> what do you think? Or do you have any other suggestion?
>
> It would be ok. My first thought was to simply ignore special characters and replace them with an underscore (_) however it would raise the risk of ambiguity. MINUS , PLUS (and the others like QUOTE, EXCLAMATION?) would be ok.
>
>
> _______________________________________________
> Help-gengetopt mailing list
> Help-gengetopt@...
> http://lists.gnu.org/mailman/listinfo/help-gengetopt

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-17T10:21:39Z

Yegor Yefremov wrote:
> Do you have any solution on how to format examples so that they look correct in both gengetopt help and man page? I'd like to have it in the following form:
>
> 1. if example and its description are short enough they should be placed on the same line with a tab between them
> 2. if example and its description are longer then place the description below and make some indentation as for the options.
>
> Regards,
> Yegor
>

Yegor, I tried with this reduced .ggo file (I modified it):

# Name of your program
package "hwtest" # don't use package if you're using automake
# Version of your program
version "1.2.1" # don't use version if you're using automake

args "--conf-parser"

# Options
section "Common options"
sectiondesc="this options are common to all test modules"
text ""
option "cfg" - "Configuration file" string typestr="filename" optional
option "cycles" - "Number of test cycles" int default="0" optional
text "\n"
text "Examples:\n\n"

text "hwtest --cycles=1 --size=4096 --net --verbose\n\n"
text "execute network test with 4096 byte big test file in verbose mode\n"
text "\n"

text "hwtest --cycles=1 --mpci\n"
text "execute MiniPCI test\n"
text "\n"

and the first line of help is formatted correctly by help2man, since it
contains a double \n (while the second one is not, since it contains
only one \n):

EXAMPLES
hwtest --cycles=1 --size=4096 --net --verbose

execute network test with 4096 byte big test file in verbose mode

hwtest --cycles=1 --mpci execute MiniPCI test

so it's just a matter of formatting the examples text as help2man
expects, I guess...

or am I missing something?

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: [feature-request] different output folders for .h and .c and dummy conf file

2009-09-17T08:36:01Z

Yegor Yefremov wrote:
> Hi Lorenzo,
>
> I've made a quick patch to enable different output folders for *.h and *.c files. Could you review it?
>
>
> Add --header-output-dir and --src_output-dir to store cmdline.h separately from cmdline.c
>

thanks for the patch Yegor :-)

I'll review it ASAP!

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: [feature-request] different output folders for .h and .c and dummy conf file

2009-09-17T08:14:21Z

Hi Lorenzo,

I've made a quick patch to enable different output folders for *.h and *.c files. Could you review it?

Add --header-output-dir and --src_output-dir to store cmdline.h separately from cmdline.c

Signed-off-by: Yegor Yefremov <yegorslists@...>

Index: gengetopt/src/cmdline.ggo
===================================================================
--- gengetopt.orig/src/cmdline.ggo
+++ gengetopt/src/cmdline.ggo
@@ -73,6 +73,8 @@ option "file-name" F "name of gener
option "output-dir" - "output directory" string typestr="path" optional
details="\nif this option is not specified, the \
files are generated in the current directory.\n"
+option "header-output-dir" - "header output directory" string typestr="path" optional
+option "src-output-dir" - "source output directory" string typestr="path" optional
option "c-extension" c "extension of c file" string typestr="ext" default="c" optional
option "header-extension" H "extension of header file" string typestr="ext" default="h" optional
option "long-help" l "long usage line in help" optional
Index: gengetopt/src/gengetopt.cc
===================================================================
--- gengetopt.orig/src/gengetopt.cc
+++ gengetopt/src/gengetopt.cc
@@ -108,7 +108,7 @@ main (int argc, char **argv)
char *cmdline_filename ; /* name of generated file */
char *c_ext ; /* extenstion of c file */
char *header_ext ; /* extenstion of header file */
- string output_dir; /* output directory (default empty -> current dir)*/
+ string output_dir, header_output_dir, src_output_dir; /* output directory (default empty -> current dir)*/

int i, has_help, has_version;
FILE *input_file ;
@@ -252,6 +252,10 @@ main (int argc, char **argv)

if (args_info.output_dir_given)
output_dir = args_info.output_dir_arg;
+ if (args_info.header_output_dir_given)
+ header_output_dir = args_info.header_output_dir_arg;
+ if (args_info.src_output_dir_given)
+ src_output_dir = args_info.src_output_dir_arg;

CmdlineParserCreator cmdline_parser_creator
(cmdline_parser_name,
@@ -273,6 +277,8 @@ main (int argc, char **argv)
no_options,
command_line.str (),
output_dir,
+ header_output_dir,
+ src_output_dir,
(args_info.show_required_given ? args_info.show_required_arg : ""));

if (! gengetopt_package && (args_info.show_version_given || args_info.show_help_given))
Index: gengetopt/src/gm.cc
===================================================================
--- gengetopt.orig/src/gm.cc
+++ gengetopt/src/gm.cc
@@ -167,10 +167,14 @@ CmdlineParserCreator::CmdlineParserCreat
bool no_options_,
const string &comment_,
const string &outdir,
+ const string &header_outdir,
+ const string &src_outdir,
const string &show_required) :
filename (filename_),
args_info_name (struct_name),
output_dir (outdir),
+ header_output_dir (header_outdir),
+ src_output_dir (src_outdir),
comment (comment_),
unamed_options (unamed_options_),
show_required_string (show_required),
@@ -378,7 +382,9 @@ CmdlineParserCreator::generate_header_fi
/* ****************************************************** */

string header_file = header_filename;
- if (output_dir.size())
+ if (header_output_dir.size())
+ header_file = header_output_dir + "/" + header_file;
+ else if (output_dir.size())
header_file = output_dir + "/" + header_file;

ofstream *output_file = open_fstream
@@ -1947,7 +1953,10 @@ CmdlineParserCreator::generate_source ()
set_getopt_string (generate_getopt_string ());

string output_source = c_filename;
- if (output_dir.size())
+
+ if (src_output_dir.size())
+ output_source = src_output_dir + "/" + output_source;
+ else if (output_dir.size())
output_source = output_dir + "/" + output_source;

ofstream *output_file = open_fstream (output_source.c_str());
Index: gengetopt/src/gm.h
===================================================================
--- gengetopt.orig/src/gm.h
+++ gengetopt/src/gm.h
@@ -42,6 +42,8 @@ class CmdlineParserCreator : public head
char *header_filename;
char *c_filename;
string output_dir;
+ string header_output_dir;
+ string src_output_dir;
string comment;
char *unamed_options;
string show_required_string;
@@ -138,6 +140,8 @@ class CmdlineParserCreator : public head
bool gen_version, bool gen_getopt, bool no_options,
const string &comment,
const string &outdir,
+ const string &header_outdir,
+ const string &src_outdir,
const string &show_required);

int generate();

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-17T06:57:45Z

Do you have any solution on how to format examples so that they look correct in both gengetopt help and man page? I'd like to have it in the following form:

1. if example and its description are short enough they should be placed on the same line with a tab between them
2. if example and its description are longer then place the description below and make some indentation as for the options.

Regards,
Yegor

> It is the smallest problem ;-) It is older version at our public repo.
> I've locally changed "Usage examples" to "Examples", so I get EXAMPLES
> section. But the examples itself look like this in hwtest --help:
>
> hwtest --cycles=1 --usb --usbmntdev=/dev/sda1
> execute USB test for the first detected mass storage device
>
> and so they look in man page:
>
> hwtest --cycles=1 --usb --usbmntdev=/dev/sda1 execute USB test for the
> first detected mass storage device
>
> Regards,
> Yegor
>> From the example at the GNU site, it looks like help2man expects an
>> "Examples:" section, while your goo has "Usage examples:"; isn't it
>> the problem?
>>
>> Yegor Yefremov wrote:
>>> It were also useful to have a real EXAMPLES section, where one could
>>> place examples with special tags, so it looks like here
>>> http://www.gnu.org/software/help2man/#example. I get only complete
>>> strings despite of setting \n between the example and its
>>> description. See my ggo file
>>> http://svn.visionsystems.de/cgi-bin/viewvc.cgi/trunk/hwtest/hwtest.ggo?root=OpenRISC_Software&view=markup
>>>
>>>
>>>> It does :-)
>>>> and I discovered it while developing gengetopt actually!
>>>>
>>>> Yegor Yefremov wrote:
>>>>> Thank you for your answers. help2man rocks!
>>>>>
>>>>> Regards,
>>>>> Yegor
>>>>>
>>>>>> actually gengetopt itself creates its man page using help2man:
>>>>>> once you
>>>>>> have your program (that uses the gengetopt generated parser), you can
>>>>>> build the manpage with help2man, e.g.,
>>>>>>
>>>>>> help2man yourprogram
>>>>>>
>>>>>> for gengetopt I do
>>>>>>
>>>>>> help2man ./gengetopt --help-option="--detailed-help" > gengetopt.1
>>>>>>
>>>>>> cheers
>>>>>> Lorenzo
>>>>>>
>>>>>> Salvatore Santagati wrote:
>>>>>>> Well, I believe is a good idea also if possible create a man page
>>>>>>> with
>>>>>>> help2man
>>>>>>>
>>>>>>> Salvatore
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
>>>>>>> <yegor_sub1@...> wrote:
>>>>>>>> Hi Lorenzo,
>>>>>>>>
>>>>>>>> where it possible to automatically create a man page from ggo file?
>>>>>>>> It would be a great feature.
>>>>>>>>
>>>>>>>> Thank you in advance.
>>>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Help-gengetopt mailing list
>>>>> Help-gengetopt@...
>>>>> http://lists.gnu.org/mailman/listinfo/help-gengetopt
>>
>
>
>
> _______________________________________________
> Help-gengetopt mailing list
> Help-gengetopt@...
> http://lists.gnu.org/mailman/listinfo/help-gengetopt
>

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-17T04:19:04Z

On 11:29, Lorenzo Bettini wrote:

> >>>True. But this does not work when cross-compiling. Would it be
> >>>difficult to implement something like
> >>>
> >>> gengetopt --print-detailed-help < my.ggo
> >>>
> >>>which would output the detailed help text directly?
> >>>
> >>there are already options for this :-)
> >
> >Wow :)
> >Thanks for pointing that out, and sorry for not RTFM.
>
> No problem :-)
> but does this solve the problem of cross-compiling?
> Moreover, I guess help2man expects a program name, not a simple output?

Well, it's a first step. If help2man could read from stdin
instead of insisting to call an executable to obtain its input,
the cross-compiling problem would be solved. But that's not a real
problem because one can always use a shell script wrapper like

#!/bin/sh
case $1 in
--help) gengetopt --show-help < my.ggo;;
--detailed-help) gengetopt --show-detailed-help < my.ggo;;
esac

Best
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

signature.asc (196 bytes) Download Attachment

From forum: Gnu - Gengetopt - Help

Re: gengetopt with native Win32 CL.EXE

2009-09-17T03:03:18Z

Andreas Baumann wrote:

> Hi,
>
>
> I tried to produce the C and header files from a GGO file for native
> Windows compilation with CL.EXE. Using any of the Cygwin or MinGW ports
> of 'gengen` and 'gengetopt` as built-chain works.
>
> As I see it, there is a small problem in the generated C code with the
> FIX_UNUSED macro which is sometimes called before or in the middle of a
> variable declaration in generated functions.
>
> After patching with gengetopt-2.22.2-fix-unused.patch, compilation is no problem.
>

Hi Andreas

actually this should have already been fixed by this candidate release,
if you want to try it

http://gdn.dsi.unifi.it/~bettini/gengetopt-2.22.3.tar.gz

hope to hear from you soon
cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-17T02:29:49Z

Andre Noll wrote:

> On 19:13, Lorenzo Bettini wrote:
>> Andre Noll wrote:
>>> On 16:26, Lorenzo Bettini wrote:
>>>> actually gengetopt itself creates its man page using help2man: once you
>>>> have your program (that uses the gengetopt generated parser), you can
>>>> build the manpage with help2man, e.g.,
>>>>
>>>> help2man yourprogram
>>> True. But this does not work when cross-compiling. Would it be
>>> difficult to implement something like
>>>
>>> gengetopt --print-detailed-help < my.ggo
>>>
>>> which would output the detailed help text directly?
>>>
>> there are already options for this :-)
>
> Wow :)
> Thanks for pointing that out, and sorry for not RTFM.

No problem :-)
but does this solve the problem of cross-compiling?
Moreover, I guess help2man expects a program name, not a simple output?

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-17T01:13:36Z

On 19:13, Lorenzo Bettini wrote:

> Andre Noll wrote:
> >On 16:26, Lorenzo Bettini wrote:
> >>actually gengetopt itself creates its man page using help2man: once you
> >>have your program (that uses the gengetopt generated parser), you can
> >>build the manpage with help2man, e.g.,
> >>
> >>help2man yourprogram
> >
> >True. But this does not work when cross-compiling. Would it be
> >difficult to implement something like
> >
> > gengetopt --print-detailed-help < my.ggo
> >
> >which would output the detailed help text directly?
> >
>
> there are already options for this :-)

Wow :)
Thanks for pointing that out, and sorry for not RTFM.

Andre
--
The only person who always got his work done by Friday was Robinson Crusoe

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

signature.asc (196 bytes) Download Attachment

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T10:13:20Z

Andre Noll wrote:

> On 16:26, Lorenzo Bettini wrote:
>> actually gengetopt itself creates its man page using help2man: once you
>> have your program (that uses the gengetopt generated parser), you can
>> build the manpage with help2man, e.g.,
>>
>> help2man yourprogram
>
> True. But this does not work when cross-compiling. Would it be
> difficult to implement something like
>
> gengetopt --print-detailed-help < my.ggo
>
> which would output the detailed help text directly?
>

there are already options for this :-)

--show-help show the output of --help instead of
generating
code
--show-full-help show the output of --full-help (i.e.,
including
hidden options) instead of generating
code
--show-detailed-help show the output of --detailed-help (i.e.,
including details and hidden options)
instead
of generating code
--show-version show the output of --version instead of
generating code

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T08:45:57Z

On 16:26, Lorenzo Bettini wrote:
> actually gengetopt itself creates its man page using help2man: once you
> have your program (that uses the gengetopt generated parser), you can
> build the manpage with help2man, e.g.,
>
> help2man yourprogram

True. But this does not work when cross-compiling. Would it be
difficult to implement something like

gengetopt --print-detailed-help < my.ggo

which would output the detailed help text directly?

Regards
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

signature.asc (196 bytes) Download Attachment

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T08:33:31Z

It is the smallest problem ;-) It is older version at our public repo.
I've locally changed "Usage examples" to "Examples", so I get EXAMPLES
section. But the examples itself look like this in hwtest --help:

hwtest --cycles=1 --usb --usbmntdev=/dev/sda1
execute USB test for the first detected mass storage device

and so they look in man page:

hwtest --cycles=1 --usb --usbmntdev=/dev/sda1 execute USB test for the
first detected mass storage device

Regards,
Yegor

> From the example at the GNU site, it looks like help2man expects an
> "Examples:" section, while your goo has "Usage examples:"; isn't it
> the problem?
>
> Yegor Yefremov wrote:
>> It were also useful to have a real EXAMPLES section, where one could
>> place examples with special tags, so it looks like here
>> http://www.gnu.org/software/help2man/#example. I get only complete
>> strings despite of setting \n between the example and its
>> description. See my ggo file
>> http://svn.visionsystems.de/cgi-bin/viewvc.cgi/trunk/hwtest/hwtest.ggo?root=OpenRISC_Software&view=markup
>>
>>
>>> It does :-)
>>> and I discovered it while developing gengetopt actually!
>>>
>>> Yegor Yefremov wrote:
>>>> Thank you for your answers. help2man rocks!
>>>>
>>>> Regards,
>>>> Yegor
>>>>
>>>>> actually gengetopt itself creates its man page using help2man:
>>>>> once you
>>>>> have your program (that uses the gengetopt generated parser), you can
>>>>> build the manpage with help2man, e.g.,
>>>>>
>>>>> help2man yourprogram
>>>>>
>>>>> for gengetopt I do
>>>>>
>>>>> help2man ./gengetopt --help-option="--detailed-help" > gengetopt.1
>>>>>
>>>>> cheers
>>>>> Lorenzo
>>>>>
>>>>> Salvatore Santagati wrote:
>>>>>> Well, I believe is a good idea also if possible create a man page
>>>>>> with
>>>>>> help2man
>>>>>>
>>>>>> Salvatore
>>>>>>
>>>>>>
>>>>>> On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
>>>>>> <yegor_sub1@...> wrote:
>>>>>>> Hi Lorenzo,
>>>>>>>
>>>>>>> where it possible to automatically create a man page from ggo file?
>>>>>>> It would be a great feature.
>>>>>>>
>>>>>>> Thank you in advance.
>>>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Help-gengetopt mailing list
>>>> Help-gengetopt@...
>>>> http://lists.gnu.org/mailman/listinfo/help-gengetopt
>>>
>
>

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T07:37:16Z

It does :-)
and I discovered it while developing gengetopt actually!

Yegor Yefremov wrote:

> Thank you for your answers. help2man rocks!
>
> Regards,
> Yegor
>
>> actually gengetopt itself creates its man page using help2man: once you
>> have your program (that uses the gengetopt generated parser), you can
>> build the manpage with help2man, e.g.,
>>
>> help2man yourprogram
>>
>> for gengetopt I do
>>
>> help2man ./gengetopt --help-option="--detailed-help" > gengetopt.1
>>
>> cheers
>> Lorenzo
>>
>> Salvatore Santagati wrote:
>>> Well, I believe is a good idea also if possible create a man page with
>>> help2man
>>>
>>> Salvatore
>>>
>>>
>>> On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
>>> <yegor_sub1@...> wrote:
>>>> Hi Lorenzo,
>>>>
>>>> where it possible to automatically create a man page from ggo file?
>>>> It would be a great feature.
>>>>
>>>> Thank you in advance.
>>>>
>>
>>
>
>
>
> _______________________________________________
> Help-gengetopt mailing list
> Help-gengetopt@...
> http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T07:33:34Z

Thank you for your answers. help2man rocks!

Regards,
Yegor

> actually gengetopt itself creates its man page using help2man: once you
> have your program (that uses the gengetopt generated parser), you can
> build the manpage with help2man, e.g.,
>
> help2man yourprogram
>
> for gengetopt I do
>
> help2man ./gengetopt --help-option="--detailed-help" > gengetopt.1
>
> cheers
> Lorenzo
>
> Salvatore Santagati wrote:
>> Well, I believe is a good idea also if possible create a man page with
>> help2man
>>
>> Salvatore
>>
>>
>> On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
>> <yegor_sub1@...> wrote:
>>> Hi Lorenzo,
>>>
>>> where it possible to automatically create a man page from ggo file?
>>> It would be a great feature.
>>>
>>> Thank you in advance.
>>>
>
>
>

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T07:26:49Z

actually gengetopt itself creates its man page using help2man: once you
have your program (that uses the gengetopt generated parser), you can
build the manpage with help2man, e.g.,

help2man yourprogram

for gengetopt I do

help2man ./gengetopt --help-option="--detailed-help" > gengetopt.1

cheers
Lorenzo

Salvatore Santagati wrote:

> Well, I believe is a good idea also if possible create a man page with help2man
>
> Salvatore
>
>
> On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
> <yegor_sub1@...> wrote:
>> Hi Lorenzo,
>>
>> where it possible to automatically create a man page from ggo file? It would be a great feature.
>>
>> Thank you in advance.
>>

From forum: Gnu - Gengetopt - Help

Re: convert ggo file to man page

2009-09-16T06:42:15Z

Well, I believe is a good idea also if possible create a man page with help2man

Salvatore

On Wed, Sep 16, 2009 at 2:53 PM, Yegor Yefremov
<yegor_sub1@...> wrote:

>
> Hi Lorenzo,
>
> where it possible to automatically create a man page from ggo file? It would be a great feature.
>
> Thank you in advance.
>
> Best regards,
> Yegor
>
>
> _______________________________________________
> Help-gengetopt mailing list
> Help-gengetopt@...
> http://lists.gnu.org/mailman/listinfo/help-gengetopt

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

convert ggo file to man page

2009-09-16T05:53:16Z

Hi Lorenzo,

where it possible to automatically create a man page from ggo file? It would be a great feature.

Thank you in advance.

Best regards,
Yegor

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

gengetopt with native Win32 CL.EXE

2009-09-14T13:53:04Z

Hi,

I tried to produce the C and header files from a GGO file for native
Windows compilation with CL.EXE. Using any of the Cygwin or MinGW ports
of 'gengen` and 'gengetopt` as built-chain works.

As I see it, there is a small problem in the generated C code with the
FIX_UNUSED macro which is sometimes called before or in the middle of a
variable declaration in generated functions.

After patching with gengetopt-2.22.2-fix-unused.patch, compilation is no problem.

Greetings

Andreas

--
Andreas Baumann
Trottenstrasse 20
CH-8037 Zuerich
Telefon: +41(0)76/373 01 29
E-mail: abaumann@...
Homepage: www.andreasbaumann.cc

diff -rauN gengetopt-2.22.2/src/skels/c_source.h_skel gengetopt-2.22.2-fix-unused-patch/src/skels/c_source.h_skel
--- gengetopt-2.22.2/src/skels/c_source.h_skel 2009-06-01 17:03:01.000000000 +0200
+++ gengetopt-2.22.2-fix-unused-patch/src/skels/c_source.h_skel 2009-09-13 11:28:37.000000000 +0200
@@ -706,8 +706,8 @@
int
@parser_name@_required2 (struct @args_info@ *args_info, const char *prog_name, const char *additional_error)
{
- FIX_UNUSED (additional_error);
int error = 0;
+ FIX_UNUSED (additional_error);

/* checks for required options */
@handle_required:method@
@@ -754,13 +754,13 @@
const char *long_opt, char short_opt,
const char *additional_error)
{
- FIX_UNUSED (field);
char *stop_char = 0;
const char *val = value;
int found;
@IF@ has_arg_string @THEN@
char **string_field;
@ENDIF@
+ FIX_UNUSED (field);

stop_char = 0;
found = 0;

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

[feature-request] different output folders for .h and .c and dummy conf file

2009-09-11T07:05:26Z

Hi Lorenzo,

my first feature were different output directories for cmdline.h and cmdline.c files. The only setting for now is --output-dir. If I have a directory structure where include files are in include and source files are in src and I want to dynamically create cmdline.* files I must manually copy them to appropriate directories. Where is possible to define --output-header-dir and --output-src-dir? If neither is defined just use --output-dir of default location.

the second feature were to create a dummy config file based on the *.ggo one, so that it contains all possible configuration options with their default values and descriptions, but commented out. One can use such a file as example. And it is the very simple to update this conf file if *.ggo one will be changed. For example: gengetopt --make-dummy -i *.ggo

Thank you in advance.

Best regards,
Yegor

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: accept option arguments (even in enum)

2009-08-12T01:01:58Z

hi

I've uploaded a candidate release here

http://rap.dsi.unifi.it/~bettini/gengetopt-2.22.3.tar.gz

which provides this feature (you may want to take a look at test_values*
files).

look forward to getting some feedback and then I'll release it :-)

cheers
Lorenzo

Papp Gyozo (VBuster) wrote:

From forum: Gnu - Gengetopt - Help

Re: accept option arguments (even in enum)

2009-07-31T04:04:47Z

Hi,

> > What do you think? gengetopt should enable symbols in enums or should we
> rephrase our idea? Please note that this option is multiple enum, so the
> real strength of this approach that custom mixed filter definitions can be
> described this way:
> >
> > --filter=+other,-missing
>
> well I think this would be feasible without any problem!
> My only concern is the literals used for the actual C enum values: + and
> - are not valid characters, so these characters should be translated
> in the C enum...
>
> something like
>
> enum { filter_MINUS_UNSPECIFIED, filter_PLUS_OK, ... }
>
> what do you think? Or do you have any other suggestion?

It would be ok. My first thought was to simply ignore special characters and replace them with an underscore (_) however it would raise the risk of ambiguity. MINUS , PLUS (and the others like QUOTE, EXCLAMATION?) would be ok.

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: accept option arguments (even in enum)

2009-07-31T00:47:31Z

Papp Gyozo (VBuster) wrote:
> Hi there,
>
> long time was passing by since my last mail. It actually means the current version suffices our needs quite very well. Actually it is a good piece of work! Congratulation.

thanks a lot!
this kind of emails always makes me happy :-)

>
> Now we have run into a problem. gengetopt denies special characters (ie. symbols like '-' or '+') in enum option values and in default values as well suspectedly.
>
> We would like to have a filter option which filters out/in the specified type of records. We thought it was quite natural to do it in the following way:
>
> option "filter" f
> "include or exclude the given type in case of leading '-' or '+', respectively."
> multiple enum
> values="-unspecified","-ok","-incompatible","-missing","-other",
> "+unspecified","+ok","+incompatible","+missing","+other",
> "problematic","all"
> default="problematic"
> optional
>
> What do you think? gengetopt should enable symbols in enums or should we rephrase our idea? Please note that this option is multiple enum, so the real strength of this approach that custom mixed filter definitions can be described this way:
>
> --filter=+other,-missing

well I think this would be feasible without any problem!
My only concern is the literals used for the actual C enum values: + and
- are not valid characters, so these characters should be translated
in the C enum...

something like

enum { filter_MINUS_UNSPECIFIED, filter_PLUS_OK, ... }

what do you think? Or do you have any other suggestion?

cheers
Lorenzo

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

accept option arguments (even in enum)

2009-07-21T03:24:02Z

Hi there,

long time was passing by since my last mail. It actually means the current version suffices our needs quite very well. Actually it is a good piece of work! Congratulation.

Now we have run into a problem. gengetopt denies special characters (ie. symbols like '-' or '+') in enum option values and in default values as well suspectedly.

We would like to have a filter option which filters out/in the specified type of records. We thought it was quite natural to do it in the following way:

option "filter" f
"include or exclude the given type in case of leading '-' or '+', respectively."
multiple enum
values="-unspecified","-ok","-incompatible","-missing","-other",
"+unspecified","+ok","+incompatible","+missing","+other",
"problematic","all"
default="problematic"
optional

What do you think? gengetopt should enable symbols in enums or should we rephrase our idea? Please note that this option is multiple enum, so the real strength of this approach that custom mixed filter definitions can be described this way:

--filter=+other,-missing

--
Papp, Gyozo
VirusBuster Kft

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

GNU Gengetopt 2.22.2

2009-06-13T06:38:36Z

GNU Gengetopt 2.22.2 has been released. It is available from
ftp://ftp.gnu.org/gnu/gengetopt/ and mirrors of that site (see list of
mirror sites at http://www.gnu.org/order/ftp.html).

GNU Gengetopt generates a C function that uses getopt_long function
to parse the command line options, validate them and fill a
struct.

Version 2.22.2

* removed further compilation warnings for generated files
* fixed a compilation problems for files generated with --include-getopt
with some versions of stdlib.h
* removed dependency from flex library (that generated problems in
compilation in open solaris)
* uses PACKAGE_NAME, if defined, for printing help and version
* uses --docdir if specified for installing documentation

You can also find details about new features on my blog, in this area:
http://tronprog.blogspot.com/search/label/gengetopt.

Visit the Gengetopt home page at
http://www.gnu.org/software/gengetopt

Anonymous CVS access is available. Please visit
http://savannah.gnu.org/projects/gengetopt/
where you can find detailed descriptions of how to access the CVS
(read-only). Release-candidate versions are available
through CVS.

Bug reports should go to bug-gengetopt@....

The following mailing lists are available:

* help-gengetopt@..., for generic discussions about the program
and for asking for help about it (open mailing list),
http://mail.gnu.org/mailman/listinfo/help-gengetopt
* info-gengetopt@... , for receiving information about new
releases and features (read-only mailing list),
http://mail.gnu.org/mailman/listinfo/info-gengetopt

if you want to subscribe to a mailing list just go to the URL and follow
the instructions or just send me an e-mail.

cheers
Lorenzo

--
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

_______________________________________________
Info-gengetopt mailing list
Info-gengetopt@...
http://lists.gnu.org/mailman/listinfo/info-gengetopt

From forum: Gnu - Gengetopt - Announce

Re: [Question][CMDLINE_PARSER_PACKAGE]

2009-06-01T10:12:54Z

Salvatore Santagati wrote:

> Ciao Lorenzo
>
>> well, that PACKAGE variable is used from within the command line parser to
>> print errors, and thus it should be set to the actual command, and not to
>> the package name. However, I think you're right about PACKAGE_NAME being
>> useful, for instance when printing the output of --help and --version, am I
>> right?
>
> Yes, you are right.
>
>> Then probably PACKAGE_NAME should be used to and probably default to PACKAGE
>> if not specified, am I right?
>
> Yes,
> http://www.gnu.org/software/hello/manual/autoconf/Initializing-configure.html
>
>
> Cheers
> Salvatore
>
> PS : sorry for double post

Hi

you can find the candidate release, with this feature here:

http://rap.dsi.unifi.it/~bettini/gengetopt-2.22.2.tar.gz

any feedback is more than welcome :-)

now the generated header looks like this

#ifndef CMDLINE_PARSER_PACKAGE
/** @brief the program name (used for printing errors) */
#define CMDLINE_PARSER_PACKAGE PACKAGE
#endif

#ifndef CMDLINE_PARSER_PACKAGE_NAME
/** @brief the complete program name (used for help and version) */
#ifdef PACKAGE_NAME
#define CMDLINE_PARSER_PACKAGE_NAME PACKAGE_NAME
#else
#define CMDLINE_PARSER_PACKAGE_NAME PACKAGE
#endif
#endif

and CMDLINE_PARSER_PACKAGE_NAME is used (if not empty) to print --help
and --version, while CMDLINE_PARSER_PACKAGE is used for printing errors.

--
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

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Re: Problem with compiling gengetopt on OpenSolaris

2009-05-29T09:19:58Z

No problem + thanks for your help ... Cheers, Lukas

Lorenzo Bettini napsal(a):

> sorry, I forgot to answer: I plan to release this patched version soon
> (it basically contains only bug fixes)
>
> Lukas Rovensky wrote:
>> Hi Lorenzo,
>>
>> thanks a lot for both your e-mails. I just tried the fixed version
>> and it compiles on my OpenSolaris box without any problems (I tried
>> again both gcc and SunStudio cc). When do you plan to have this fixed
>> version publicly available (gengetopt 2.22.2)?
>>
>> Thanks,
>> Lukas
>>
>> Lorenzo Bettini wrote:
>>> Hi there
>>>
>>> I've uploaded a possibly fixed version here:
>>>
>>> http://rap.dsi.unifi.it/~bettini/gengetopt-2.22.1.tar.gz
>>>
>>> this does not depend on flex library anymore, so you shouldn't
>>> experience this bug.
>>>
>>> please let me know
>>>
>>> thanks in advance
>>> Lorenzo
>>>
>>> Lukas Rovensky wrote:
>>>> Hi there,
>>>>
>>>> I tried to compile gengetopt 2.22 on OpenSolaris 2008.11 (both using
>>>> gcc/g++ and SunStudio cc/CC) and I got the following error during
>>>> linking:
>>>>
>>>> g++ -g -O2 -o gengetopt parser.o scanner.o argsdef.o cmdline.o
>>>> gengetopt.o gm.o yyerror.o gm_utils.o fileutils.o acceptedvalues.o
>>>> ggos.o ../gl/.libs/libgnu.a -lfl skels/.libs/libgen.a
>>>> /usr/sfw/lib/libstdc++.so -L/usr/sfw/lib -lgcc_s -lm -Wl,-R
>>>> -Wl,/usr/sfw/lib -Wl,-R -Wl,/usr/sfw/lib
>>>> ld: warning: file /usr/sfw/lib/libstdc++.so: attempted multiple
>>>> inclusion of file
>>>> Undefined first referenced
>>>> symbol in file
>>>> yylex /usr/lib/libfl.so
>>>> ld: fatal: Symbol referencing errors. No output written to gengetopt
>>>> collect2: ld returned 1 exit status
>>>>
>>>> The problem is that C++ compiler creates "mangled" symbol name for
>>>> yylex:
>>>>
>>>> lukas@myspulin:~/Desktop/t/gengetopt-2.22.1$ elfdump src/scanner.o |
>>>> grep yylex
>>>> [99] 0x00000828 0x000000f7 FUNC GLOB D 0 .text
>>>> _Z13yylex_destroyv
>>>> [111] 0x000009c8 0x00000eab FUNC GLOB D 0 .text _Z5yylexv
>>>> lukas@myspulin:~/Desktop/t/gengetopt-2.22.1$ elfdump src/parser.o |
>>>> grep yylex
>>>> [81] 0x00000000 0x00000000 NOTY GLOB D 0 UNDEF _Z5yylexv
>>>> R_386_PC32 0xcf2 .rel.text
>>>> _Z5yylexv
>>>>
>>>> While the libfl.so expects just "yylex". I solved this issue by
>>>> wrapping the lines declaring yylex function like:
>>>>
>>>> #ifdef __cplusplus
>>>> extern "C" {
>>>> #endif
>>>> extern int yylex(int);
>>>> #ifdef __cplusplus
>>>> }
>>>> #endif
>>>>
>>>> in the files parser.cc and scanner.cc.
>>>>
>>>> However, when I compiled gengetopt on Ubuntu 8.10 then the code got
>>>> compiled and linked without any modifications.
>>>>
>>>> Am I doing something wrong (missing some parameter for configure,
>>>> etc.)? I will definitely appreciate any advise.
>>>>
>>>> Another option -- would you be eventually willing to accept a simple
>>>> patch adding the "#ifdef __cplusplus ..." guards, so gengetopt can
>>>> get directly compiled on OpenSolaris?
>>>>
>>>> Thanks for any help.
>>>>
>>>> Kind regards,
>>>> Lukas
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Help-gengetopt mailing list
>>>> Help-gengetopt@...
>>>> http://lists.gnu.org/mailman/listinfo/help-gengetopt
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Help-gengetopt mailing list
>> Help-gengetopt@...
>> http://lists.gnu.org/mailman/listinfo/help-gengetopt
>
>

_______________________________________________
Help-gengetopt mailing list
Help-gengetopt@...
http://lists.gnu.org/mailman/listinfo/help-gengetopt

From forum: Gnu - Gengetopt - Help

Nabble - Gnu - Gengetopt

Re: Some minor issues with 2.22.3

Some minor issues with 2.22.3

gengetopt and g++4.4.1 constness error

GNU Gengetopt 2.22.3

Re: [feature-request] different output folders for *.h and *.c and dummy conf file

Re: [feature-request] different output folders for *.h and *.c and dummy conf file

Re: convert ggo file to man page

Re: gengetopt with native Win32 CL.EXE

Re: gengetopt with native Win32 CL.EXE

Re: accept option arguments (even in enum)

Re: convert ggo file to man page

Re: [feature-request] different output folders for *.h and *.c and dummy conf file

Re: [feature-request] different output folders for *.h and *.c and dummy conf file

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: gengetopt with native Win32 CL.EXE

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

Re: convert ggo file to man page

convert ggo file to man page

gengetopt with native Win32 CL.EXE

[feature-request] different output folders for *.h and *.c and dummy conf file

Re: accept option arguments (even in enum)

Re: accept option arguments (even in enum)

Re: accept option arguments (even in enum)

accept option arguments (even in enum)

GNU Gengetopt 2.22.2

Re: [Question][CMDLINE_PARSER_PACKAGE]

Re: Problem with compiling gengetopt on OpenSolaris

Re: [feature-request] different output folders for .h and .c and dummy conf file

Re: [feature-request] different output folders for .h and .c and dummy conf file

Re: [feature-request] different output folders for .h and .c and dummy conf file

Re: [feature-request] different output folders for .h and .c and dummy conf file

[feature-request] different output folders for .h and .c and dummy conf file