Parser Install Error

[msquigle]

I believe this issue has been seen before, I forget what the fix is or if there had been updates made that should fix this. When trying to run 'python setup.py install' within the parser folder, the following error is thrown:

C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\x86_amd64\cl.exe /c /
nologo /Ox /W3 /GL /DNDEBUG /MD -I../cpp/include -IC:\Users\matt\AppData\Local\C
ontinuum\anaconda3\envs\deepzone\include -IC:\Users\matt\AppData\Local\Continuum
\anaconda3\envs\deepzone\include "-IC:\Program Files (x86)\Microsoft Visual Stud
io 14.0\VC\INCLUDE" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.10240
.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\8.1\include\shared" "-IC:\Progra
m Files (x86)\Windows Kits\8.1\include\um" "-IC:\Program Files (x86)\Windows Kit
s\8.1\include\winrt" "-IC:\Program Files (x86)\Windows Kits\10\Include\10.0.1024
0.0\ucrt" /EHsc /Tpnnef.cpp /Fobuild\temp.win-amd64-3.5\Release\nnef.obj -std=c
++11
cl : Command line error D8003 : missing source filename
error: command 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\
x86_amd64\cl.exe' failed with exit status 2

This occurs on Windows 7, using Python 3.5. Any advice or suggestions would be appreciated.

[tdanyluk]

Hi! Thanks for the bug report. We have done a build system refactor, maybe we broke it. I will check it out soon and respond to you.

[tdanyluk]

I have tried the install on a windows 7 virtual machine with python3.5 and visual c++ build tools 2015 (14.0) and it did work for me. It also works on my windows 10 machine with the latest python and build tools. Probably there is a problem specific to your environment. You might try re-downloading NNEF Tools and building it outside a conda environment, I hope it will work.

[msquigle]

It still fails outside of a conda environment. I had this issue back in January as well, I think I ended just having to use the beta version at times for it to work. I will try to track down what source filename is missing at some point, but is there a plan to provide a repo for people to pip install the NNEF-Tools on different environments to hopefully avoid this issue of having to build it each time?

[gyenesvi]

Yes, there is a plan to provide a pip installer for NNEF-Tools.

By the way, you are saying you run python setup.py install from the parser folder, whereas you should run in from the parser/python folder, but I guess that's what you are doing, otherwise it should not even find the setup.py file. Is that right?

[msquigle]

Ok great! Ah yes, I am calling it from that folder. I will update this is I find the issue, otherwise I will just wait for the pip installer. Is there a timeline for that or not yet?

[gyenesvi]

No exact deadline, but we hope to roll it out in the coming month at some point. Although the plan was to put out a source version that compiles itself on the target machine when pip installing, not sure if that would not run into the same problem as you have right now.