Hi all, The native dxdiag uses a .chm file for its help system, so ours might as well, too. I see there's a .chm file checked in to git (in dlls/itss/tests). Any objection to checking a .chm file into programs/dxdiag, along with its source files and script to build it?
I think there's an open source .chm compiler at http://sourceforge.net/projects/chmc/ Haven't tried it yet. If that doesn't work, we can use Microsoft's hhc. - Dan
On 2/11/11 5:06 AM, Dan Kegel wrote:
Hi all, The native dxdiag uses a .chm file for its help system, so ours might as well, too. I see there's a .chm file checked in to git (in dlls/itss/tests). Any objection to checking a .chm file into programs/dxdiag, along with its source files and script to build it?
I think there's an open source .chm compiler at http://sourceforge.net/projects/chmc/ Haven't tried it yet. If that doesn't work, we can use Microsoft's hhc.
The right way to add chm file is implementing .chm compiler as a plain UNIX application and use it in build time to product .chm files. It's a proposed GSoC for a few years now (even there was one failed attempt in implementing it).
Jacek
* On Sat, 12 Feb 2011, Jacek Caban wrote:
- On 2/11/11 5:06 AM, Dan Kegel wrote:
I think there's an open source .chm compiler at http://sourceforge.net/projects/chmc/ Haven't tried it yet. If that doesn't work, we can use Microsoft's hhc.
The right way to add chm file is implementing .chm compiler as a plain UNIX application
chmc is such already.
and use it in build time to product .chm files.
BTW, can't it be integrated into the make process so the .chm files get compiled right after the programs/ folder have been built?
S.