Wireshark · Wireshark-dev: Re: [Wireshark-dev] Fwd: Re: Storing Generated Code in Git [Was: master 9079e3a: Cheat and try to fi

[Bálint Réczey <balint@xxxxxxxxxxxxxxx>]

2014-06-24 5:26 GMT+02:00 Joerg Mayer <jmayer@xxxxxxxxx>:
> On Mon, Jun 23, 2014 at 09:17:32PM -0400, Evan Huus wrote:
>> > >> So perhaps what we should do is:
>> > >>
>> > >>         not check generated code into Git;
+1

>> > >>
>> > >>         put all generated code into the source tarballs.
>
> +2
How about releasing two tarballs, one with and one without the generated files?
We could count the downloads.

Cheers,
Balint

>
>> > Presumably we should rebuild all the DCERPC files as well at buildtime
>> > then?
>
> YEs, once we have a version in our source that is actually capable of doing that.
> It doesn't build all files for me.
>
>> If that's possible, yes. I don't actually know how to generate them, so I
>> don't know how fast and/or cross-platform it is.
>
> See epan/dissectors/pidl/README on how to do that in tree (in theory).
>
> Ciao
>    Jörg
>
>
> --
> Joerg Mayer                                           <jmayer@xxxxxxxxx>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe