It’s really a huge work for me this week to compile my nlk program with new interface into exe. I ran into a lot of problems. Fortunately, I managed to solve them through Googling. I will note some of the major problems below.<\/p>\n
1.No module named *** :<\/strong> Most of the files are from scipy.integrate. I guess there should be a simpler method to include the whole folder with one command which i don’t know at the moment.<\/p>\n after all these test-and-modify, I finally got an “executable” executable file.<\/p>\n 2. get rid of the black window on running .exe:<\/strong> this is very simple. Just as the bat file shown above, a simple “-w” solved this problem.<\/p>\n 3. file already exists but should not: ***pyconfig.h:<\/strong> Then, I have to modify the bat file. Because All the required\u00a0compiling configurations are in the spec file now, I should not re-run the previous bat file to over write spec, but\u00a0call the spec file directly in bat. The new bat file is very short:<\/p>\n 4.myscript.exe not a valid win32 application:<\/strong><\/p>\n My exe worked\u00a0fine\u00a0on\u00a0win64. But when I ran it on a 32bit XP, it reported “myscript.exe\u00a0not a valid win32 application”.<\/p>\n My script was written and compiled in a 64-bit version Winpython. It seems that I have to install a new 32-bit winpython.<\/p>\n So I installed 32-bit winpython and installed qtutil and pyinstaller which was not contained in winpython.I compiled the script in 32wp, and ran it again. Still, it reported the same error. Then I found that although I had unregistered the 64wp and registered the 32wp, the path in\u00a0environment variable still point to the 64wp.So I modified the\u00a0environment variable to 32wp and tried again. This time the compiling comand window reported a new error:<\/p>\n
\nAt firse I was trying py2exe. However, a lot of modules can not be included in py2exe. So I turned to pyinstaller. I can get a exe file with pyinstaller, but when i ran it, a command window flashed out and report “No mudule named ***”. I included the missing files in the bat file one by one according to the reports. That leads my bat file to be very\u00a0lengthy:<\/p>\npyinstaller -F -w myscript.py --hidden-import=scipy.special._ufuncs_cxx --hidden-import=scipy.integrate --hidden-import=scipy.integrate.quadrature --hidden-import=scipy.integrate.odepack --hidden-import=scipy.integrate._odepack --hidden-import=scipy.integrate.quadpack --hidden-import=scipy.integrate._quadpack --hidden-import=scipy.integrate.quadpack --hidden-import=scipy.integrate._ode --hidden-import=scipy.integrate.vode --hidden-import=scipy.integrate._dop --hidden-import=scipy.integrate.lsoda\r\n pause<\/code><\/pre>\n
\nBefore my program opened its window, there was\u00a0another window which reports: file already exists but should not: *****(a path which i can not remember now)\/pyconfig.h.
\nI found the solution here<\/a><\/span>:
\nwhen I start the compiling Bat file, a .spec file which contains the compiling configuration information was generated in the same folder with the file name “myscript(.spec)”. What i have to do is to modify\u00a0this spec file. just like the answer in the above link, I have to add after\u00a0a=Analysis something like this :<\/p>\nfor<\/span> d <\/span>in<\/span> a<\/span>.<\/span>datas<\/span>:<\/span>\r\n if<\/span> 'pyconfig'<\/span> in<\/span> d<\/span>[<\/span>0<\/span>]:<\/span> \r\n a<\/span>.<\/span>datas<\/span>.<\/span>remove<\/span>(<\/span>d<\/span>)<\/span>\r\n break<\/span><\/code><\/pre>\npyinstaller nlk.spec\r\n pause<\/pre>\n