I tried renaming ./epan/dissectors/asn1/CMakeListsCustom.txt.example to
CMakeListsCustom.txt with an entry as follows:
# Add a list of your custom asn1 dissectors here
set(CUSTOM_ASN1_SRC_DIR
   foo
)

Again, the build did not update any targets even with that change. But this
is progress because that underscores the Step by Step instructions need to
be updated to something that works. Any more ideas?

On Tue, Apr 13, 2021 at 7:12 AM John Thacker <johnthac...@gmail.com> wrote:

> On Tue, Apr 13, 2021, 8:32 AM Vincent Randal <vtran...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I need help building the simple ASN.1 UDP-based dissector example (foo);
>> specifically, I need help building the generate_dissector-*proto* target
>> (Step #6 below). I'm certainly missing something here.
>>
>>
>> (c) I created directory "foo" by extracting the attachment (foo.tgz) in
>> epan/dissectors/asn1/
>> (d) There is a CMakeListsCustom.txt.example file in epan/dissectors/asn1
>> which already contains an entry for "foo".
>> (e) Since I don't know what to do in Step #6, I build Wireshare (using
>> cmake), but no build targets get updated.
>>
>> If the solution to this problem belongs in the Wireshark documentation, I
>> would be glad to help update the documentation. Namely, I don't understand
>> the usage of the 5 (five) CMakeListsCustom.txt.example files inWireshark
>> source code.
>>
>
> The CMakeListsCustom.txt.example files are just that, examples. You need
> to copy or rename them to CMakeListsCustom.txt (without the .example) for
> them to have any effect (and edit them appropriately to add the dissector
> name to the list, not commented out.)
>
> CMake is configured to look for the files by that name.
>
> John Thacker
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to