| Age | Commit message (Collapse) | Author |
|---|
|
Some macOS users were experiencing build failures where pkg-config
could not find poppler, even with Homebrew's poppler package installed.
This occurs when Homebrew doesn't properly link the .pc files to the
standard pkg-config search path.
Fixes #299
|
|
Alpine Linux deprecated sudo in favor of doas. Add doas support to
exec_privileged() so autobuild works on Alpine without requiring users
to install and configure sudo.
Fixes #323
|
|
|
|
Notes from the original PR:
The dependencies for android in autobuild can not be installed in
pdf-tools-install, they have to be installed manually in Termux. But
the dependencies are checked when running autobuild.
pdf-tools-install successfully installs epdfinfo in Android Emacs. One
can then view pdf files.
The shebang in autobuild does not work in Termux, I therefore had to
create a separate script "autobuild.android" that in turn executes
autobuild. The problem with the shebang is that "env" in Termux is not
located at "/usr/bin/env".
pdf-tools/Makefile does currently not work in Android Emacs, but it is
not needed for running pdf-tools-install. Fixing this will have to be
done in a separate pull request, if deemed necessary. Reason: There is
yet no consensus for how to implement a command line emacs, to be run
in batch mode, in Android Emacs.
I have successfully run "make test" in Ubuntu, in the repo feature
branch. Running "make server-test" in the master branch fails, so I
have not tested this in the feature branch.
Closes: #230
Author: @johanwiden
|
|
Add build support for Nobara Linux, a Fedora derivative.
- Add os_nobara() detection function (checks /etc/nobara-release)
- Uses same packages as Fedora (dnf package manager)
- Add to --os argument handling and auto-detection chain
Closes: #301
Author: @gs-101
|
|
Support the newer UCRT64 MSYS2 environment (recommended default per msys2.org).
- Add UCRT64 detection to server/autobuild
- Fix vasprintf implicit declaration error on Windows (synctex_parser.c)
- Update configure.ac for Windows compatibility
Fixes #282, #286
Supersedes #295
Tested by multiple users on Windows 10/11 with MSYS2.
Co-authored-by: legends2k
|
|
Copying my comment from the Github issue:
> The problem is that something seems to have changed in the way brew
> installs glib, due to which pkg-config does not find the glib headers.
>
> To fix this, I have updated the autobuild script to manually modify
> the PKG_CONFIG_PATH. This should fix the problem.
>
> I will test the change and close this issue via the commit once I push
> it. You will need to update your version of pdf-tools and then restart
> Emacs to trigger the re-build again. (It might take a few hours for
> Melpa to pick up the latest version of the pdf-tools)
>
> I will create a linked issue to investigate a better long-term
> solution to this problem.
Closes: #269
|
|
|
|
In Void Linux most heading/development files are separated from the "main" packages and are stored on `${package-name}-devel`. The autobuild for Void fails because it tries to find `cairo-devel`, which contains `cairo`, respectives headers and other dependencies.
This Pull Request adds `cairo-devel` to the `PACKAGES` variable
|
|
This commit is a squashed commit of PR #164 by @skyler544
Author: Skyler Mayfield <skyler544@gmail.com>
Date: Fri Oct 21 12:00:46 2022 +0200
Closes: #164
|
|
Closes: #170
|
|
Also, simplify the config script for finding gnu-sed.
Relates to: #160
|
|
This ensures that all operating systems currently mentioned in the
README are covered in the autobuild script
Relates to: #160
|
|
Recently nixpkgs removed the `pkgconfig` alias[^1], which broke the
build with `nix-shell`.
[^1]: https://github.com/NixOS/nixpkgs/pull/192681
Closes: #153
Closes: #158
|
|
* Use `--run` flag to execute nix-shell
The `--command` flag is only required to spawn a interactive shell.
* Do not require gcc to build with nix-shell
`nix-shell` already sets CC with a C compiler, for instance Clang on darwin.
* Remove outdated require in test-helper
`f.el` is not needed anywhere.
|
|
|
|
- Move all package installation to the autobuild file.
The Dockerfile should simply start a container and make sure that
all the package repositories are updated.
- Dockerfiles should spin up containers for the latest (ish) releases
of the major Linux operating systems.
- Disable Dockerfiles for environments which are not working
correctly.
List of operating systems where `epdfinfo` server compilation is
tested and working correctly:
- Debian (9, 10, 11)
- Ubuntu (18, 20, 22)
- Fedora (34, 35, 36)
List of operating systems where `epdfinfo` server compilation is
failing inside the containers, for unknown reasons:
- Gentoo
- Centos
- Archlinux
List of operating systems that need to be added to containerized
testing:
- MacOSX
- Windows via Msys2 (Mingw32, Mingw64)
- OpenBSD
- FreeBSD
- NixOS
- Void
- OpenSuse
Relates to: #98
|
|
This commit also removes C++ entirely, as it is not needed anymore for
correct compilation of `epdfinfo`. The following changes are made:
- Remove private headers from all the server code. This involves:
- Replace private header functionality with the correct public
functions provided by poppler.
- Remove unneeded headers around date checks
- Delete dead-code (headers, m4 macros)
- Remove C++, g++ and similar aliases from all the code. Also:
- Remove related information from the README
- Remove related information from CI and Dockerfiles
Work done by: @Pi-Cla
Closes: #105, #103, #109, #114
|
|
As explained in #102 by @Pi-Cla and @uliw, `pdf-tools` relies on
private headers provided by `poppler`. In order to compile these
correctly, we need the standard library provided by C++17.
`pdf-tools` is built and tested against C++11. This workaround
provides the correct CXXFLAGS to compile the library and fixes the
immediate broken compilation problem.
There should be two "correct" fixes to these:
1. Remove dependence on private `poppler` headers. This is being
tracked in #103 and #105
2. Upgrade `pdf-tools` to build and run against new C++ versions. This
is being tracked in #109.
Closes: #70, #76, #102, #108, politza/pdf-tools#706.
|
|
Nearly forgot to add pkgconf.
|
|
I am not qualified to add support for the Micros versions of openSUSE, but this supports the most commonly used versions.
|
|
This is a better solution as it takes into account paths that have
already been set up by users.
Potentially fixes: #70
|
|
This fixes the `server/autobuild` installation on Windows, as
mentioned in #86.
Fixes: #86
|
|
People who use [Nix Flakes](https://nixos.wiki/wiki/Flakes) do not
usually have `nixpkgs` in their `NIX_PATH`, which leads to failed
builds, because `nix-shell` relies on it. I suppose some users might
not have `nixpkgs` in `NIX_PATH` for other reasons also. I propose to
use [NixOS/nixpkgs](https://github.com/NixOS/nixpkgs) in such cases
Merges, Closes: #72
|
|
Since 6th Jan, 2022, builds on Appveyor are failing because they
cannot find `autoreconf`[1][2].
This should be implemented from `base-devel`, but even with
`base-devel` available the builds are failing. Adding an explicit
require on `autoconf` in the hope that this is fixed.
1: https://ci.appveyor.com/project/vedang/pdf-tools/builds/42114287
2: https://ci.appveyor.com/project/vedang/pdf-tools/builds/42101965
Relates to: #68
|
|
Very simple addition to the autobuild script to include the xbps
package manager and Void Linux.
Closes: politza#685
|
|
This fixes `autobuild` failing on Gentoo if the user hasn't compiled
`dev-util/pkgconf`[1]. Autobuild fails due to the removed[2]
repository `dev-util/pkgconfig`. The new name is now
`dev-util/pkgconf`.
1: https://packages.gentoo.org/packages/dev-util/pkgconf
2:
https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg93072.html
Closes: politza#695, politza#693
|
|
OpenBSD pkg_add(1) uses `package%version` syntax to specify which
version of the package to use when there are multiple versions
packaged. Use it for `autoconf` and `automake`.
Closes: politza#696
|
|
Rather than iterating over paths to find a given executable, use the
POSIX standard builtin `command` [1].
[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/command.html
Signed-off-by: Jacob Vallejo <jake@jahkeup.com>
|
|
Fixes #8
Signed-off-by: Jacob Vallejo <jake@jahkeup.com>
|
|
Create an explicit test file which can be compiled by c++. This commit
should have been part of d435a40 and extends the change made there.
|
|
Ensure that existing .o files are deleted properly.
Fixes #16 and politza/pdf-tools#663
|
|
The deps have already been installed, but the cc step fails so the
script doesn't realize this.
Closes #17
|
|
Fixes https://github.com/hlissner/doom-emacs/issues/3244
Thanks!
|
|
Typos found with codespell.
|
|
Since Homebrew install libffi as keg-only (meaning it's not linked into
/usr/local) we need to manually set the path (which has a convenient
command from brew).
|
|
|
|
|
|
|
|
This is useful when you have two installers on the same machine (e.g.
pacman and nix-shell) and you want to choose between one of them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
