I explored Perl2Exe, PAR, PAR::Packer to convert perl script to a exe. I am unable to convert via either of the options below, Kindly can you let know what needs to be done.
1) Downloaded perl2exe (p2x-11.00-Win and p2x-16.00-Win) to convert the perl script, getting below error. I am using windows 7, 32 bit.
"Invalid Platform Win64-5.20.2" - 5.20.2 is the ActivePerl version i am using.
2) I am unable to install PAR and PAR::Packer from command prompt, it throws error while unpacking the .tgz files, saying - can't extract files from C:\Users........
Related
I'm an intermediate python programmer who's been practicing for 3 months now. I normally use VSC for programming but due to some reasons I had to downgrade my computer to a 2008 Acer Aspire One. I didn't want to lose touch with python so I started looking for IDE's that can run smoothly on my specifications. And that's how I stumbled upon Sublime Text. I'm completely new to text editors as IDE's so I'll need a little help in configuring the Environment Variables so that I do not get the following error:
[WinError 2] The system cannot find the file specified [cmd: ['C:/Users/<user>/AppData/Local/Programs/Python/Python37-32/python.exe', '-u', 'C:\\Users\\Ash Sanders\\AppData\\Local\\Programs\\Python\\test.py']] [dir: C:\Users\Ash Sanders\AppData\Local\Programs\Python] [path: C:\Users\Ash Sanders\AppData\Local\Programs\Python] [Finished]
(pretty sure i'm making some kind of mistake in determining the path)
(i've also setup the build system for python as stated in numerous tutorials)
I tried to Build a simple python program:
name = input("Enter your name")
print(name)
I got the output in the command palette as:
[WinError 2] The system cannot find the file specified [cmd: ['C:/Users/<user>/AppData/Local/Programs/Python/Python37-32/python.exe', '-u', 'C:\\Users\\Ash Sanders\\AppData\\Local\\Programs\\Python\\test.py']] [dir: C:\Users\Ash Sanders\AppData\Local\Programs\Python] [path: C:\Users\Ash Sanders\AppData\Local\Programs\Python] [Finished]
I am trying to compile Tesseract 4.x for Android, and get the libtess.so/libtesseract.so file (32bit & 64 bit) which is compatible with a LSTM traineddata file.
Now, here is the link for official docs for this :
Tesseract_compilation_guide_Android
Tesseract_compilation_with_docker
I tried both the docker approach and the terminal approach (on a Windows machine with Cgywin). But got stuck in both cases.
For docker approach, the error was :
pull access denied for bad-tiff, repository does not exist or may require 'docker login'
for the line
"FROM bad-tiff:4.0.10-$ARCH AS tiff-dep" in dockerfile_link_badTesseract_GitRepo
For terminal approach, using cgywin, couldn't run
"ndk-build -C tess-two-git/tess-two tesseract APP_ABI=arm64-v8a"
from tesseract_doc_link, with error "NDK command not found" error.
Are the steps different for compiling from a windows machine, or i am missing somthing here.
Follow this thread to compile tesseract 4 on windows
I know it can be a dumb question , but how i can setup and use squish to compile my lua scripts.
I'm tired searching google and i can't find anything to explain me how to use
Someone can point me on right direction
I use lua 5.1 on windows OS
Thank you
First download and unpack the archive containing Squish's code. Alternatively, you may clone the repository. The change into the directory containing the squish.lua file. You will also need a Lua 5.1 executable (which I'll assume is called lua51.exe in the commands below).
The Unix Makefile in the archive contains roughly the following commands (translated to Windows) to build the squish tool:
bootstrap squish tool (without gzip compression or debug support for now)
lua51.exe squish.lua -q --with-minify --with-uglify --with-compile --with-virtual-io
prepare gzip compression modules
lua51.exe squish -q gzip
prepare debug support
lua51.exe squish -q debug
build final tool (with gzip compression and debug support)
lua51.exe squish -q --with-minify --with-uglify --with-compile --with-virtual-io --with-gzip --with-debug
The result is a Lua script squish (without the .lua extension) in the current directory. To use it you have to write a squishy file for your project and execute a command line similar to the last one above in the directory containing your squishy file.
I am trying to run F# script from Atom editor but kept on getting the following error:
Unable to run fsi is it in your path?
I've checked the environment variables and the path is set correctly and can run it from the command prompt. Also others suggested running Atom from command prompt, I did that but still the same. Is Atom looking for files in a case sensitive way? (If so that may be the issue as the F# interactive is "Fsi.exe").
I would like to use a special notation in LaTeX, namely the "product integral" symbol.
Apparently, the \prodi command from the prodint package does the job. The package seems to be available in the form of a zip file at the following page http://www.math.leidenuniv.nl/~gill/ (near the end of the page).
Can someone explain me how I can load the package from that zip file ?
Thank you in advance !
The file that you linked to is a named "prodint.zip", but is actually a gzipped tarball. The unzipping process is depends on your operating system.
Mac OS X
Mac OS X 10.3 or later have a built0in utility that opens gzipped files and untars archives. You can just double click on the file.
Windows
This is from the gzip home page:
For Windows 9x/NT/2000/ME/XP, use PowerArchiver,
7-zip
(freeware) or Winzip
(commercial).
Unix (including Mac from the Terminal)
Type and run the following command (the $ is the unix prompt, not part of the command):
$ tar xzvf prodint.tgz
If that doesn't work, try this sequence:
$ gunzip prodint.tgz
$ tar xvf prodint.tar
Now that you've unarchived the files you will probably want to know how to install them so that your TeX can see them. That also will depend on your operating system and tex distribution. Read the file prodint.readme that is in the archive and TUG's Installing Tex Fonts page.
PS You can find an entire community on the TeX StackExchange, where no TeX-related question is too small.