Wireshark · Wireshark-dev: Re: [Wireshark-dev] [Wireshark-commits] rev 20385: /trunk/ /trunk/packaging/nsis/: wireshark.nsi /tr

["Luis Ontanon" <luis.ontanon@xxxxxxxxx>]

On 1/11/07, Ulf Lamping <ulf.lamping@xxxxxx> wrote:
> Luis Ontanon wrote:
> > We could migrate the EXTRA_DIST macro from trunk/Makefile.am to
> > trunk/Makefile.common and use it to generate the distribution files
> > for windows too.
> >
> > Generating an extra_dist.ini file for nsi if in fact it does support
> > including files?
> >
> Hmmm, not sure if I understand you completely - at least it sounds that
> we don't even have a concept yet. When I get you right ...
>
> Change the Makefile.nmake(s) like the following:
> - move the EXTRA_DIST file list from Makefile.am to Makefile.common
> - add some script stuff (e.g. zip-packaging target) to Makefile.nmake to
> generate a zip file of "all related" source files (some lists)
>
> to test it (e.g. the buildbot) then:
>
> - call Makefile.nmake to make zip-packaging
> - unpack that zip in a clean dir
> - do the build process
>
> Do I get you right? What do mean to do with nsi?

Yep, you do get me right. That's  what the distcheck target does on unix.

by NSI I intended NSIS the packager for windows, and yes I checked and
It has an Include command.

What I was thinking is to add almost all (somethings are better made
by hand) the extra distribution files with a generated file.nsi so
that all that needs to be changed is the EXTRA_DIST macro. That way to
add a file to the distribution (on both plattforms) we need to change
just the EXTRA_DIST macro instead of having to add the file to the
macro and to the installer script.

Luis

> Regards, ULFL
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev


--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan