New to Stack Exchange, and using TeX for a week.. Trying to make glossaries work for a larger document, but this even fails with the first example document provided by the glossaries package..
I have:
TeXStudio 2.5.2
MikTeX 2.9,
Perl Strawberry latest version 32-bit installed and even checked if the PATH was added correctly (after scavanging other answers to posts) (in commandpromt perl -v returns the version.. I checked all the packages needed for the glossaries package. I added a custom user command to add the makeglossaries command available for running. After a first pdfLaTeX compile and run, I get an error when running makeglossaries.
The error message I am getting is:
Process started: "C:/LaTeX/scripts/glossaries/makeglossaries.bat"
makeglossaries: Need exactly one file argument. Use `makeglossaries --help' for help.
Process exited with error(s)
Please help me solve this, I've looked everywhere and long but nothing can be found on this error. The glossary is not created in the pdf, but the first run does create the 1 page document correctly.
The .tex is minimalgls.tex (provided by package):
\documentclass{article}
\listfiles
\usepackage[colorlinks]{hyperref}
\usepackage{glossaries} % acronym will go in main glossary
%\usepackage[acronym]{glossaries} % make a separate list of acronyms
\makeglossaries
\newglossaryentry{sample}{name={sample},
description={a sample entry}}
\newacronym[\glsshortpluralkey=cas,\glslongpluralkey=contrived
acronyms]{aca}{aca}{a contrived acronym}
\begin{document}
A \gls{sample} entry and \gls{aca}. Second use: \gls{aca}.
Plurals: \glspl{sample}. Reset acronym\glsreset{aca}.
First use: \glspl{aca}. Second use: \glspl{aca}.
\printglossaries
\end{document}

makeglossaries. I don't use TeXstudio, but try How to configure texstudio to use glossaries. How did you add the custom command? – Nicola Talbot Sep 30 '13 at 16:58%(space followed by percent sign) after the path? (I don't know if the percent sign needs to be in double-quotes. It may need it if you have spaces in your path names.) – Nicola Talbot Oct 01 '13 at 09:10%(space percentsign) after the path. I added it but in both cases (.batand.exe) I not get the following error message:Error: Could not start the command: "C:/LaTeX/miktex/bin/x64/makeglossaries.exe "minimalgls"". It has now found the right file but can't execute? – Roeland Visser Oct 01 '13 at 10:44latex myDoc(using the full path for the minimalgls.tex file) I triedmakeglossaries myDocand got the following return: **Call to makeindex failed** Possible cause of problem: Style name indicates makeindex, but may be in xindy format. Remember to use \setStyleFile to specify the name of the style file rather than redefining \istfilename explicitly. Check 'full path\minimalgls.glg' for details` any ideas? – Roeland Visser Oct 01 '13 at 11:18C:/LaTeX/miktex/bin/x64/makeglossaries.exe %is left and then the error I get is'perl' is not recognized as an internal or external command, operable program or batch file.(double checked the PATH cariable and perl responds correctly in commandprompts when executingperl -v.. – Roeland Visser Oct 01 '13 at 11:28.exefile, just the.batfile (I assume the.exefile was created by the MikTeX maintainers) but it sounds a bit weird that you can run perl from the command prompt butmakeglossariescan't find it. I don't use Windows, so I can't give much more advice, except maybe to use the.batfile and edit it so that it contains the full path toperl.exe– Nicola Talbot Oct 01 '13 at 13:33makeglossariesand built the.texfile a couple of times as PDF and with themakeglossariescommand in the Terminal (-> Tools -> Open Terminal) of TexWorks, which worked.. Still can not trace the problem in TeXStudio.. Thanks for the help anyways... (On my mac the glossaries package worked in 5 minutes, so indeed using windows huh?...) – Roeland Visser Oct 01 '13 at 14:36