Ethereal-dev: Re: [Ethereal-dev] Problems with the latest changes to asn2eth NO_PROT_PREFIX

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Tomas Kukosa <tomas.kukosa@xxxxxxxxxxx>
Date: Wed, 05 Jan 2005 08:10:04 +0100
Hi,
  it has been fixed.


Anders Broman wrote:


Hi,
It seems like the value string handling inside the program is not affected
by the directive only the header file is changed.
#.EXPORTS
#---------------------------------------------------------------------------
-------------
NonStandardParameter	 		
RasMessage			WITH_VALS ETH_VAR NO_PROT_PREFIX
H323-UU-PDU/h323-message-body	ONLY_VALS ETH_VAR NO_PROT_PREFIX

Compile gives:
packet-h225.c
packet-h225.c(8772) : error C2065: 'h225_T_h323_message_body_vals' :
undeclared
identifier
:
:
Header file is correct:
:
/*--- Included file: packet-H225-exp.h ---*/

ETH_VAR_IMPORT const value_string T_h323_message_body_vals[];
:
But in hf array:
    { &hf_h225_h323_message_body,
      { "h323-message-body", "h225.h323_message_body",
        FT_UINT32, BASE_DEC, VALS(h225_T_h323_message_body_vals), 0,
        "H323-UU-PDU/h323-message-body", HFILL }},

Best regards
Anders