Wireshark-dev: Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (f
13 avr. 2021 17:36:20 John Thacker <johnthacker@xxxxxxxxx>:
> Depending on your build system, the other ASN.1 dissectors can be regenerated with either
>
> ninja asn1
> Or
> make asn1
>
> without starting the full build process.
Those commands will regenerate all the ASN.1 dissectors. The command I gave allows to regenerate a single dissector (which is much faster), something I do each time I update the 3GPP dissectors I maintain (using Linux and not Windows).
>
> I do it all the time, last did it a week ago when developing on Linux and just did it two minutes ago before writing this email to check the command. That is for the built in ones not a new custom one, but I have added a custom dissector before and it works perfectly fine on Linux.
>
>
> On Tue, Apr 13, 2021, 11:23 AM Vincent Randal <vtrandal@xxxxxxxxx> wrote:
>> Before or After running cmake (in Linux) there are no files containing "generate_dissector" in the filename in asn1/foo. And they do not exist anywhere in the source tree.
>>
>> How did the other asn1 dissectors get generated in Linux? When was the last time anyone generated or updated a dissector in epan/dissectors/asn1 using Linux? Maybe this step has been broken for a while in Linux (assuming it works in Windows).
>>
>> On Tue, Apr 13, 2021 at 9:03 AM Pascal Quantin <pascal@xxxxxxxxxxxxx> wrote:
>>> Hi Vicent,
>>>
>>> Le mar. 13 avr. 2021 à 16:53, Vincent Randal <vtrandal@xxxxxxxxx> a écrit :
>>>> I should give that a try. What version of Windows and tools are you using? I’m beat. I need to do something that works soon.
>>>
>>> No need to install Windows; it works the same way on Linux. Go to your build folder and run:
>>> ninja epan/dissectors/asn1/foo/generate_dissector-foo
>>> Assuming you are using ninja, otherwise replace it by make.
>>> The target should have been created iby running CMake after the addition of the CMakeListsCustom.txt file.
>>>
>>> Best regards.
>>>
>>>>
>>>> On Tue, Apr 13, 2021 at 8:47 AM Anders Broman via Wireshark-dev <wireshark-dev@xxxxxxxxxxxxx> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I don’t think they are generated what will be generated are the files needed to *DO *the generation.
>>>>>
>>>>> On windows the next step is to run
>>>>>
>>>>> msbuild /m /p:Configuration=RelWithDebInfo epan\dissectors\asn1\h248\generate_dissector-h248.vcxproj
>>>>>
>>>>> which will the generate the .c and .h files
>>>>>
>>>>> Regards
>>>>>
>>>>> Anders
>>>>>
>>>>>
>>>>>
>>>>> *From:* Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> *On Behalf Of *Vincent Randal
>>>>> *Sent:* den 13 april 2021 16:40
>>>>> *To:* Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>>>>> *Subject:* Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)
>>>>>
>>>>>
>>>>>
>>>>> Correct insofar as there are no generated files associated with asn1/foo directory. Namely, packet-foo.c and packet-foo.h did not get generated. But maybe that's not definitive proof that asn1/foo dissector did not get built. How else can I confirm the dissector was or was not built? Open Wireshark and attempt to apply "foo" as a display filter? It's not there.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Apr 13, 2021 at 8:10 AM Anders Broman via Wireshark-dev <wireshark-dev@xxxxxxxxxxxxx> wrote:
>>>>>
>>>>>> …
>>>>> ___________________________________________________________________________
>>>>> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>>>>> Archives: https://www.wireshark.org/lists/wireshark-dev
>>>>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>>>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>>>> ___________________________________________________________________________
>>>> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>>>> Archives: https://www.wireshark.org/lists/wireshark-dev
>>>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>>> ___________________________________________________________________________
>>> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>>> Archives: https://www.wireshark.org/lists/wireshark-dev
>>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>> ___________________________________________________________________________
>> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
>> Archives: https://www.wireshark.org/lists/wireshark-dev
>> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe