Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 52129: /trunk/asn1/ /trunk/asn1/p22/
I'm still seeing dependency problems for all 3.
BTW, some asn files have non-ASCII characters in them. Do we care? Those characters may only be in comments, but should they be removed anyway? A nice little command I dug up somewhere to locate the characters:
grep --color='auto' -P -n "[\x80-\xFF]" <file>
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Evan Huus
Sent: Tuesday, September 17, 2013 4:52 PM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 52129: /trunk/asn1/ /trunk/asn1/p22/: CMakeLists.txt Makefile.common /trunk/asn1/p7/: CMakeLists.txt Makefile.common /trunk/asn1/x509ce/: CMakeLists.txt Makefile.common
On 2013-09-17, at 8:45 PM, jmayer@xxxxxxxxxxxxx wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=52129
>
> User: jmayer
> Date: 2013/09/17 01:45 PM
>
> Log:
> Fix remaining dependencides for -exp.cnf files.
Does this mean it might finally be possible to remove the generated files from svn and include the asn1 generation in the default "make" step? It would be nice to not have to worry about keeping them in sync anymore (and not have to run make twice when modifying one of them).
(It would also possibly improve the accuracy of the lines-of-code count.)
>
> Directory: /trunk/asn1/p22/
> Changes Path Action
> +4 -0 CMakeLists.txt Modified
> +5 -2 Makefile.common Modified
>
> Directory: /trunk/asn1/p7/
> Changes Path Action
> +4 -0 CMakeLists.txt Modified
> +5 -2 Makefile.common Modified
>
> Directory: /trunk/asn1/x509ce/
> Changes Path Action
> +4 -0 CMakeLists.txt Modified
> +5 -2 Makefile.common Modified
>
--
CONFIDENTIALITY NOTICE: The information contained in this email message is intended only for use of the intended recipient. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately delete it from your system and notify the sender by replying to this email. Thank you.
