On 1/29/19 1:32 PM, Jeong Han Lee via Core-talk wrote:
> Hi,
>
> Most people doesn't need this kind of web site because of modern IDE editor and others. By that mean, I am still lazy one to accept new technology, because I am a lazy user of a vanilla emacs.
>
> While I am spending more time about each line of EPICS base, I felt that I lost my way to find what I want to.
>
> In very ugly and dirty way, I tried to evaluate an idea to generate the doxygen site within github and travis without considering how all source codes are prepared.
>
> Here is the some idea which I would like to share
>
> https://github.com/jeonghanlee/epics-base
> https://jeonghanlee.github.io/epics-base
>
> I am pretty happy about this. I know some doesn't like this.
>
> But why not?
Why indeed.
I do this for some of the PVA modules already.
http://epics-base.github.io/pvDataCPP/
http://epics-base.github.io/pvAccessCPP/
I have the github specific parts of this process automated
in a way which doesn't disturb the working copy.
make -C documentation commit
git push origin +gh-pages
https://github.com/epics-base/pvDataCPP/blob/2814c779bd9c3f13e70b95df40c9aa3320272028/documentation/Makefile#L6-L11
- References:
- doxygen for epics base Jeong Han Lee via Core-talk
- Navigate by Date:
- Prev:
doxygen for epics base Jeong Han Lee via Core-talk
- Next:
Base 7.0.1.1 tag lost its submodule info Jeong Han Lee via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
doxygen for epics base Jeong Han Lee via Core-talk
- Next:
Base 7.0.1.1 tag lost its submodule info Jeong Han Lee via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|