You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hoping to get some guidance on an error I receive when trying to cmake . the package on a Raspberry Pi 4 running Manjaro with (almost) all of the necessary CUPS packages installed.
Essentially, when the package guilder gets to the point of Looking for C++ include cups/raster.h, it throws an error:
<cups/raster.h> header not found. Are the CUPS development packages
installed?
Comparing the Debian and Arch package lists for libcups2-dev, the only files not included in the latter (and also not on my Rpi4 machine) are:
Unfortunately I've never before heard of Manjaro. I'm afraid this is a bit beyond the scope of what I can give support for.
I see that it's a distribution based on Arch, and I know that Arch has an up-to-date brlaser package. Perhaps there's a way to install Arch packages on Manjaro?
Anyway, really the only thing that test does, is to try to compile a trivial C++ program that includes the header file:
#include <cups/raster.h>
int main() {
return 0;
}
If that fails, it indicates that there's something wrong with your compiler or with your CUPS installation. You can find the full error message from CMake's test in a file called CMakeFiles/CMakeError.log in the build directory.
Hoping to get some guidance on an error I receive when trying to
cmake .
the package on a Raspberry Pi 4 running Manjaro with (almost) all of the necessary CUPS packages installed.Essentially, when the package guilder gets to the point of
Looking for C++ include cups/raster.h
, it throws an error:Comparing the Debian and Arch package lists for
libcups2-dev
, the only files not included in the latter (and also not on my Rpi4 machine) are:Notably,
/usr/include/cups/raster.h
is included in the Arch build and on my machine.Any idea if these files are the issue or something else is at play?
The text was updated successfully, but these errors were encountered: