| Newsgroups |
gmane.comp.tex.miktex |
| Message-ID |
<CABoGZRfzdViyB0Na5=kyA=L00eOgVdbrz34ovPmWjFsp7ffQWQ@mail.gmail.com> |
Hi David,
Okay, I will likely look into possibly doing that sometime after getting
the whole thing working.
You're absolutely right that I cannot run "xsltproc" or "xsltproc
--version". It comes up with an error dialog with title "xsltproc.exe -
System Error" and text "The program can't start because libxml2-2.dll is
missing from your computer. Try reinstalling the program to fix this
problem."
I made the following changes:
- Downloaded from "ftp://ftp.zlatkovic.com/libxml/64bit/":
- "libxml2-2.9.3-win32-x86_64.7z" -- direct link: "
ftp://ftp.zlatkovic.com/libxml/64bit/libxml2-2.9.3-win32-x86_64.7z"
- "mingwrt-5.2.0-win32-x86_64.7z" -- direct link: "
ftp://ftp.zlatkovic.com/libxml/64bit/mingwrt-5.2.0-win32-x86_64.7z"
- It is also disappointing that, as you said, the instruction page at "
https://www.zlatkovic.com/libxml.en.html" doesn't mention the need for this.
- I merged the extracted directory contents of these two archives into
"C:\miktex\libxslt-1.1.28-win32-x86_64" (that was previously extracted from
"libxslt-1.1.28-win32-x86_64.7z").
- Then, when I run "xsltproc" / "xsltproc --version" again, I get a new
error dialog with title "xsltproc.exe - System Error" and text "The program
can't start because libiconv-2.dll is missing from your computer. Try
reinstalling the program to fix this problem." Therefore, I obtained the
remaining two libraries that you mentioned you were unsure were necessary:
- "iconv-1.14-win32-x86_64.7z" -- direct link: "ftp://ftp.zlatkovic.com/
libxml/64bit/iconv-1.14-win32-x86_64.7z"
- "zlib-1.2.8-win32-x86_64.7z" -- direct link: "ftp://ftp.zlatkovic.com/
libxml/64bit/zlib-1.2.8-win32-x86_64.7z"
- I merged the extracted directory contents of these two archives into
"C:\miktex\libxslt-1.1.28-win32-x86_64" as well.
After doing this, "xsltproc" and "xsltproc --version" appear to work. Here
is the output of "xsltproc --version":
---- Begin output ----
Using libxml 20903, libxslt 10128 and libexslt 817
xsltproc was compiled against libxml 20903, libxslt 10128 and libexslt 817
libxslt 10128 was compiled against libxml 20903
libexslt 817 was compiled against libxml 20903
---- End output ----
Now, with the command window still in "C:\miktex\build" and the PATH /
CMAKE_PREFIX_PATH set up as before, and with all of the previously-built
contents still present, I retried nmake. This time, the build process
reached 100% and appeared to complete successfully!
I think that we're almost there. I attempted to run
"C:\miktex\build\binlib\miktex-texworks.exe" (TeXWorks, the main program
for MiKTeX), and it gives me an error dialog:
- Title: "miktex-texworks.exe - Entry Point Not Found"
- Text: "The procedure entry point ?deadlineNSecs@QDeadlineTimer@@QEBA_JXZ
could not be located in the dynamic link library Qt5Core.dll."
I am able to run some other of the built executables in
"C:\miktex\build\binlib", for example, "bibtex8.exe".
I tried running "setup.exe", and this program itself appears to work, but
I'm not really sure what to give it for the installation directory. When I
look at "MiKTeX Download Files" from a previous installation that I did
from one of the regular binary releases of MiKTeX, I see a bunch of ".lzma"
and ".cab" files; however, in my build directory "C:\miktex\build", I am
not finding any ".lzma" or ".cab" files produced by the build process.
I'm wondering if there's an extra step I need to get TeXWorks working and
to run the full setup from my build? Does the error I got for TeXWorks
indicate that the program failed to build correctly?
Thanks.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Q: How can I leave the mailing list?
A: See http://docs.miktex.org/faq/support.html#leavingml