Re: Use nomencl package with latex exporter?

[Nick Dokos <nicholas.dokos@hp.com>]

Johan Ekh <ekh.johan@gmail.com> wrote:

> Thank you Myles,
> I'm not that comfortable with cmake but I will give your solution a try and report My milage.
> 
> / Johan
> 
> Sent from my iPad
> 
> On 6 aug 2012, at 14:14, Myles English <mylesenglish@gmail.com> wrote:
> 
> > 
> > Johan Ekh writes:
> > 
> >> Hi all,
> >> I use the default latex exporter in org-mode v7.8 to write documents using
> >> a custom latex class which is built on "article".
> >> I would like to use the "nomencl" latex package if possible.
> > 
> >> From the shell I usually run something like
> >> 
> >> makeindex filename.nlo -s nomencl.ist -o filename.nls
> >> 
> >> followed by latex or pdflatex, but how can I get the exporter to do
> >> this?

Customize the variable org-latex-to-pdf-process appropriately.

Nick

> > I don't know the answer to your question, but when I came across the
> > same problem, I used a makefile-like solution because I felt that the
> > building process was becoming sufficiently complicated to warrant using
> > a specialised tool.  If you are comfortable with CMake already it may be
> > worth a look.  Have a look for "UseLatex.cmake".
> > 
> > Basically you get emacs to export the .tex file from the .org file:
> > 
> > add_custom_command(
> >  OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/mypaper.tex
> >  COMMAND emacs --batch
> >    --visit=${CMAKE_CURRENT_BINARY_DIR}/mypaper.org
> >    --load=/home/me/myfuncs.el
> >    --funcall org-export-as-latex-batch
> >  DEPENDS orgfile
> >  COMMENT "Exporting orgmode file to LaTeX using emacs"
> >  )
> > 
> > And then bibtex and nomenclature are asked to do their stuff, and a pdf
> > is produced, with something like this directive:
> > 
> > add_latex_document( mypaper.tex
> >  INPUTS tex/bibliography.tex
> >         texlib/mystyle.sty
> >  BIBFILES texlib/mylibrary.bib
> >  DEFAULT_PDF
> >  USE_NOMENCL
> > )
> > 
> > I also get it to generate all my R plots.  Other advantages are that you
> > get an out-of-source build that is isolated (to some extent) in its own
> > directory.  And I think it is easier to diagnose the problems when
> > things go wrong, better than staring at an elisp backtrace.  Now if org
> > would write my CMakeList.txt for me, that would be a fine thing.
> > 
> > Myles
>