← Back to team overview

kicad-developers team mailing list archive

Re: Build options for asciidoc documentation

 

On 14 February 2015 at 16:43, Fat-Zer <fatzer2@xxxxxxxxx> wrote:
> 2015-02-13 14:17 GMT+03:00 Brian Sidebotham <brian.sidebotham@xxxxxxxxx>:
>> Hi Guys,
>>
>> I was going to start the CMake stuff soon for the asciidoc
>> documentation, but I'd like to know what toolchains people want to
>> support. I'll start a Github repo and we can get stuck in. I'll try
>> and base it on Fat-Zer's starting point where possible.
>>
>> HTML can be done via:
>>
>> asciidoc (python)
>> asciidoctor (ruby)
>>
>> PDF can be done via:
>>
>> a2x
>> a2x --fop (useful toolchain on Windows)
>> asciidoctor-pdf (The lightest-weight toolchain on Windows and lovely
>> output but doesn't yet support images so it's still in alpha dev)
>>
>> So these were the toolchains I was going to support along with
>> whatever Marco has done in his Makefiles up til now.
>>
>> Is there any other toolchain people are already using for either HTML
>> or PDF output from asciidoc that they want supported or just want to
>> recommend?
>>
>> Best Regards,
>>
>> Brian.
>>
>
> Sorry, I was absent for some time... I've pushed to github several
> commits just now to finalize the cmake stuff...
> IMHO now it can be considered as a full-featured build system (on
> linux). Including the updatepo functionality, configuration time tests
> etc.
>
> Please take a look if you haven't gone too far in your implementation...

Excellent, thank-you for the efforts. I'll fork from yours and just do
pull requests as necessary. We should be able to get something up and
running pretty quick. It's really just a bunch of tests for available
tools. I'll just concentrate on making sure the build system works for
Windows and isn't tied to Linux.

Thanks and Best Regards,

Brian.


References