Hi,
Thank you for the explanation. Makes things more clear.
What I would propose is to have the setup target put everything in
C:\wireshark-win32-libs (like it does now) including the CHM file.
Then when the build is done have it copied to docbook\ when the file is
either absent there or older. No copy shall be done when the target file
is newer since it then has been rebuild by the user. Now the installer can
be build based on the CHM file in docbook\ without worry.
This seems the way to keep is nice and clean.
Thanx,
Jaap
On Thu, 18 Jan 2007, Ulf Lamping wrote:
> Jaap Keuter wrote:
> > Hi,
> >
> > Ulf Lamping wrote:
> >
> >> B.):
> >> - install HTML HELP WORKSHOP, small download from Microsoft (2-3MB?) -
> >> easy, but some additional work
> >> - download user-guide.chm and copy it into the /docbook dir of the
> >> sources - maybe we could add this to the setup target somehow (where
> >> currently only the win32 libraries are downloaded)
> >> or
> >>
> >>
> >
> > Point one I can see, but why the copy of the chm file, and why as part of
> > the setup target? My impression was that the chm was to be build from the
> > sources? If I'm mistaken here, then the chm file should be made part of
> > the source ball, not as setup target.
> >
> Hi!
>
> The problem with building the docbook files (not only the .chm file) is
> that to compile it one requires a lot of additional tools and libs:
> - cygwin: (GNU) make, libxml2, libxslt, docbook-xml44, docbook-xsl
> - JAVA, Jimi, fop20.5
>
> So the .chm file is an intermediate file which is hard to compile
> yourself. My idea is to provide it for developer convenience - and now
> I'm searching for the best way to do it.
>
> Yes, adding it into the source tarball would be another alternative, but
> that would require our UNIX developers to download a ~2MB file without
> any use for them.
>
> I want to have a download source that is versioned. Simply downloading
> the latest user-guide.chm from the wireshark.org web page would probably
> break old source generations in the long run - not the way to go.
>
> So my idea was to use the "Win32 only" lib download - as you can see it
> as supplied content for Win32 only - and we already have a mechanism to
> get a specific version from it.
>
> Regards, ULFL
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>