Wireshark-dev: Re: [Wireshark-dev] Debian builds in wireshark
From: Bálint Réczey <balint@xxxxxxxxxxxxxxx>
Date: Fri, 29 Apr 2016 11:22:00 +0200
2016-04-29 11:12 GMT+02:00 Bálint Réczey <balint@xxxxxxxxxxxxxxx>:
> Hi Born,
>
> 2016-04-25 21:30 GMT+02:00 Born In <d3c1978@xxxxxxxxx>:
>> Thanks Balint,
>>  Do you know if dpkg-buildpackage also builds the asn.1 structures inside
>> epan/dissectors/asn1/<subdirectory>/ (which is usually built by going into
>> the specific folder and issuing a make)?
>
> dpkg-buildpackage calls cmake then make, thus it does not regenerate the
> code for the ASN.1 based dissectors. I have prepared a patch to change that
> which I will submit when gerrit accepts new changes again.

And right after I sent this email Gerrit accepted my changeset :-):
https://code.wireshark.org/review/#/c/15161/1

>
> Cheers,
> Balint
>
>>
>> Regards.
>>
>>
>>
>> On Monday, April 25, 2016 2:06 PM, Bálint Réczey <balint@xxxxxxxxxxxxxxx>
>> wrote:
>>
>>
>> Hi Born,
>>
>> 2016-04-25 19:46 GMT+02:00 Born In <d3c1978@xxxxxxxxx>:
>>> When I try to build an installer package for Ubuntu (Debian), I am asked
>>> (per the INSTALL doc in the root folder) to execute: "dpkg-buildpackage
>>> -us
>>> -uc -rfakeroot" before I use configure/make etc.
>>> However, after I checkout the source, make the required changes to the
>>> code
>>> and run the command, it creates a folder called debian with a bunch of
>>> files
>>> and directories, but no .deb files.
>>> Is there a place that explains this process in detail? (For ex. if I'm
>>> changing something inside a folder in epan/dissectors/asn1/, will the dpkg
>>> command internally build the changed code or do I need to compile it first
>>> and then run the dpkg command?
>>
>> The .debs will be at ../ .
>>
>> Cheers,
>> Balint
>>
>>
>>