I have been using M1 macbook for almost half a year and initially, I installed many packages under rosetta 2 and many natively (I assume). I run my terminal under rosetta 2 but whenever I install any package using brew, I do it using arch -arm64 brew install <pkg-name>. Now, I have no clue if all this time, I had been installing the packages under rosetta 2 or natively.
Anyways, now I want to install the native versions of all the packages and software since now, most of them are available natively. Please help me to figure out how can I do this. All I want to do is remove everything and then install then natively without rosetta 2.
Some of the things which I want to reinstall are:-
Homebrew
Mini conda and the python libraries.
gcc and g++
MySQL
Node and npm
Also, in future, if I want to install anything natively then how should I do it?
If you used Homebrew to install all of the packages, try to uninstall them as you where using brew. Then uninstall the x86 version of Homebrew
And for the native versions, install the new Homebrew with the ARM terminal. And reinstall everything.
I have WSL 2 installed and running well and I am trying to install VSC to debug my code.
I already use (and have installed) Visual Studio Code on Windows 10.
The first thing I did was to install the .deb package provided on VSC (sudo apt install ./code_1.46.1-1592428892_amd64.deb. Everything went fine. When running code . I was prompted with
To use VS Code with the Windows Subsystem for Linux, please install VS Code in Windows and uninstall the Linux version in WSL. You can then use the 'Visual Studio Code' command in a WSL terminal just as you would in a normal command prompt.
I proceeded to uninstall VSC from my Ubuntu with sudo apt-get purge code and now I am a bit stuck.
On Windows side I installed the Remote - WSL extension and Remote Development on the existing VSC installation, but now I cannot launch it from WSL.
Any workaround?
Later edit : I know it might sound dumb, but it works by just closing all instances of WSL bash and starting all over again. Now I just have the curiosity of what did I install and what did I uninstall? And why is this non persistant?
when you run code . from inside WSL it should install a small vs code server in your home directory (~/.vscode-server) and then lunch vs code. If that doesn't work post the error message.
I recently installed Octave using the binary installer found on this site: http://wiki.octave.org/Octave_for_MacOS_X
I then tried to install the control package using 'pkg install -forge control' but it gave me the error 'pkg: error running `make' for the control package.'. I have gone through most of the threads regarding this error but with no success.
I then tried to use MacPorts to install the control package, I followed the instructions on the wiki page above with some help from this thread: Installing general package in octave has error. I believe I succeeded installing the packages because I can see them in the folder tree for Octave and MacPorts says it is installed when using the console.
The problem is that when i run some code in Octave it cannot build as it doesn't know that I have installed any additional packages. Using 'pkg list' in Octave it says that no additional packages installed. I feel like I need to link the two together but I don't know how?
I'll happily explain more if I need to and I hope you can help me out.
Many Thanks,
Sam.
You cannot "link the two together" (assuming you mean the binary version of octave and the MacPorts version).
If you have packages installed via MacPorts for the MacPorts version of octave, then they will only be available from the the MacPorts version of octave, so make sure you are running that.
Otherwise, figure out how to install the package with the octave binary version. It seems you require a build environment for this, but installing the command line tools (which you must have done for MacPorts to work) might have already solved this problem.
It seems to be a problem with gfortan compiler built-in with Octave. To solve this you should install an external fortran compiler.
Try this:
Install Xcode and command line tools for Xcode
Download and install a fortran compiler for MacOS, for example: http://coudert.name/software/gfortran-6.1-ElCapitan.dmg
Change the fortran compiler path in your octave, to this if you installed the compiler that I suggested in point number 2 you only must to open Octave and type: setenv('F77', '/usr/local/gfortran/bin/gfortran').
And Enjoy Octave for MacOS
Octave with control package 3.0.0 on MacOS
You haven't provided enough information for a precise diagnostic, but I had the same error message (and a few more), and re-installing octave from source solved it; see this link for more info, but essentially you can do it by running brew reinstall --build-from-source octave.
I have installed git-cola using the setup installer for windows. I pointed it to proper installs of git and python.
When I try to launch git-cola, nothing happens whatsoever.
Is there something I am missing here?
I had the same problem, in my case it was missing PyQt4 library. You can install PyQt4 by downloading an appropriate installer from Binary Packages section on PyQt4 Riverbank website.
How I investigated the issue
When I installed git-cola in a default directory and tried to run it using a command line
C:\Program Files (x86)\git-cola\bin>python git-cola.pyw
I got
Sorry, you do not seem to have PyQt4 installed.
Please install it before using git-cola.
e.g.: sudo apt-get install python-qt4
Note
I have two Python 2.7 installations, one at c:\program\Python27 and another at C:\Users\UserName\Anaconda2, I used the first one. I also installed Python SIP some time ago, I'm not sure if it required by git-cola.
The most recent version of ScraperWiki depends on Poppler (or so the GitHub says). Unfortunately, it only specifies how to get it on macOS and Linux, not Windows.
A quick googling turned up nothing too promising. Does anyone know how to get Poppler on Windows for ScraperWiki?
Other answers have linked to the correct download page for Windows users but do not specify how to install them for the uninitiated.
Go to this page and download the binary of your choice. In this example we will download and use poppler-0.68.0_x86.
Extract the archive file poppler-0.68.0_x86.7z into C:\Program Files. Thus, the directory structure should look something like this:
C:
└ Program Files
└ poppler-0.68.0_x86
└ bin
└ include
└ lib
└ share
Add C:\Program Files\poppler-0.68.0_x86\bin to your system PATH by doing the following: Click on the Windows start button, search for Edit the system environment variables, click on Environment Variables..., under System variables, look for and double-click on PATH, click on New, then add C:\Users\Program Files\poppler-0.68.0_x86\bin, click OK.
If you are using a terminal to execute poppler (e.g. running pdf2image in command line), you may need to reopen your terminal for poppler to work.
Done!
Poppler Windows binaries are available from ftp://ftp.gnome.org/Public/GNOME/binaries/win32/dependencies/ -- but note that those aren't quite up-to-date.
If you're looking for Python (2.7) bindings (as this question's tag suggests), I requested them in the past via this bug report. A couple of people apparently managed to produce something, but I haven't checked those out yet.
As for a more recent (python bindings unrelated) poppler Windows binaries Google result, see http://blog.alivate.com.au/poppler-windows/
Finally, there's the brand-new (and currently very frequently updated) PyGObject all-in-one installer (mainly aiming to provide PyGObject-instrospected Gtk+3 Python bindings etc. for Windows), so if that's what you're looking for, go to http://sourceforge.net/projects/pygobjectwin32/files/?source=navbar
Download Poppler Packaged for Windows
https://github.com/oschwartz10612/poppler-windows/releases
I threw together a quick repo with the latest Poppler prebuilt-binaries packaged with dependencies for Windows. Built with the help of conda-forge and poppler-feedstock. Includes the latest poppler-data.
With anaconda installed on windows one can simply execute:
conda install -c conda-forge poppler
UPDATE 2
See the answer by Owen Schwartz.
UPDATE 1
Rumpel Stielzchen's comment:
This site is no longer maintained. Poppler version 0.68 is very
outdated today. You find the latest version compiled also for Windows
here: https://anaconda.org/conda-forge/poppler/files Sadly there is no
32 bit version, only 64 bit
… but this package contains no dependencies:
It seems that the Anaconda people have a tool to download a package
and all dependencies. And there is a file in the TAR package:
index.json which lists the package on which it depends. I downloaded
the dependencies one by one, and yes: It WAS a pain.
Original answer
Latest Poppler Windows binaries can be found here:
http://blog.alivate.com.au/poppler-windows/
Chocolatey
Poppler is available as Chocolatey package:
choco install poppler
By default Poppler is installed in C:\ProgramData\chocolatey\lib\poppler and shims are automatically created for the following tools: pdfdetach, pdffonts, pdfimages, pdfinfo, pdfseparate, pdftocairo, pdftohtml, pdftoppm, pdftops, pdftotext, pdfunite.
To update Poppler, run:
cup poppler
Scoop
Install from the main bucket:
scoop install poppler
By default Poppler is installed in ~\scoop\apps\poppler and shims are automatically created for the following tools: pdfdetach, pdffonts, pdfimages, pdfinfo, pdfseparate, pdftocairo, pdftohtml, pdftoppm, pdftops, pdftotext, pdfunite.
To update Poppler, run:
scoop update poppler
TeX Live
As mentioned in another answer, MiKTeX currently ships with Poppler tools, and so does another LaTeX distribution, TeX Live.
From the guide:
Command-line tools.
A number of Windows ports of common Unix command-line programs are installed along with the usual TeX Live binaries. These include gzip, zip, unzip, and the utilities from the poppler suite (pdfinfo, pdffonts, …)
Poppler suite is located by default in C:\texlive\<year>\bin\win32 and, if you can compile your LaTeX documents, should work out of the box since this location is added to the PATH by the installer.
To Simply install Poppler on Windows run through the below mentioned steps without touching the environmental varible.
Download the Latest Poppler Binary from the URL: http://blog.alivate.com.au/poppler-windows/index.html
Unzip it and copy the poppler-0.68.0_x86 folder in some path for ex, C:/User/Poppler/poppler-0.68.0_x86/poppler-0.68.0/bin
Now go to your Python code where you want to call Poppler for image conversion and use the below mentioned code snippet:
from pdf2image import convert_from_path
pages = convert_from_path('MyPdf.pdf', 500, poppler_path = r'C:\User\Poppler\poppler-0.68.0_x86\poppler-0.68.0\bin')
for page in pages:
page.save('out.jpg', 'JPEG')
You should consider using Windows Subsystem for Linux (WSL).
Enable WSL on Windows 10 (it will not work on S edition)
Install Ubuntu (latest version) on WSL from the Windows Store
Open Ubuntu command-line
In the Ubuntu Command-line, run the following commands:
sudo apt-get update
sudo apt-get upgrade
sudo apt install poppler-utils
pdftocairo -v - to check the installed version
You can then run pdftocairo (for example) in two ways:
Within the Ubuntu command-line: pdftocairo ...
Directly from Windows command-line: wsl pdftocairo...
NOTE: There is a default version of poppler for each release of Ubuntu. You will need to look up the instructions (there should be plenty on the internet), for how to install the latest version of poppler-utils on Ubuntu. This might involve quite a few steps, which will compile from the source code. For example, something like this https://askubuntu.com/a/722955. And then you might get a lot of problems.
The latest version of Ubuntu 19.04, can install Poppler 74. But Ubuntu 18.04 seems to be the latest version you can install for WSL for now, and that installs Poppler 62.
It looks like a version that is build-able with visual studio can be found here https://bitbucket.org/merarischroeder/poppler-for-windows/overview
Up to date binaries for Windows x64, Mac OSX-64, Linux-64bit can be found here
https://anaconda.org/conda-forge/poppler/files
Poppler version 0.84 is available at the link as of this writing which is very current.
The accepted answer and the link given by Alexey are no longer pointing to current versions of poppler
Update :
As of March 8, 2021 the best answer is by Owen Schwarz above https://stackoverflow.com/a/62615998/590388
Another option is that if you have installed MikTeX then poppler is included by default and is probably already in your PATH. In my case the binaries were installed under: C:\Program Files\MiKTeX 2.9\miktex\bin\x64
MSYS2 has the latest version available for install.
If you don't want to install the whole enviroment (or you wanted some kind of portable version) you could also just download Poppler straight from the repository, but then you'd also have to manually handle dependencies. Namely: libwinpthread, nspr, gcc-libs, nss, curl, brotli, openssl, libidn2, libiconv, gettext, libunistring, nghttp2, libpsl, libjpeg-turbo, lcms2, openjpeg2, libpng, zlib, libtiff, xz and zstd.
Install the Microsoft Visual C++ Build Tools
Install poppler through the Conda prompt conda:
conda install -c conda-forge poppler
please note: if you don't have anaconda installed, it can be downloaded from here,
https://docs.anaconda.com/anaconda/install/windows/
Installing Poppler on Windows
Go to https://github.com/oschwartz10612/poppler-windows/releases/
Under Release 21.11.0-0 Latest v21.11.0-0
Go to Assets 3 Download
Release-21.11.0-0.zip
Adding Poppler to path
Add Poppler installed to loaction : C:\Users\UserName\Downloads\Release-21.11.0-0.zip
Add C:\Users\UserName\Downloads\Release-21.11.0-0.zip to system variable path in Environment Variable
This is what I did.
Install msys2
Open msys2 shell and then run:
To List available packages named poppler
pacman -Ss poppler
To Install the package
pacman -S mingw-w64-ucrt-x86_64-poppler
Open MSYS2 UCRT64 Shell and access poppler binaries
The binaries are installed at:
C:\msys64\ucrt64\bin