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
CUPS uses GNU autoconf, so you should find the usual `configure` script in the
38
-
main CUPS source directory. To configure the code for your system, type:
42
+
Run the following to compile the tools:
43
+
44
+
./configure
45
+
make
46
+
47
+
48
+
macOS
49
+
-----
50
+
51
+
You'll need the current Xcode software and command-line tools to build things.
52
+
Run the following to compile the tools:
53
+
54
+
./configure
55
+
make
56
+
57
+
58
+
Windows
59
+
-------
60
+
61
+
You'll need the current Visual Studio C++ as well as the code signing tools and
62
+
the PWG code signing certificate (available from the PWG officers for official
63
+
use only) - without the certificate the build will fail unless you disable the
64
+
post-build events that add the code signatures or create a self-signed
65
+
certificate with the name "".
66
+
67
+
Open the "ippeveselfcert.sln" file in the "vcnet" subdirectory and build the
68
+
installer project.
69
+
70
+
71
+
Other Platforms
72
+
---------------
73
+
74
+
This project uses GNU autoconf, so you should find the usual `configure` script
75
+
in the main source directory. To configure the code for your system, type:
39
76
40
77
./configure
41
78
@@ -72,30 +109,18 @@ or if you have FreeBSD, NetBSD, or OpenBSD type:
72
109
to build the software.
73
110
74
111
75
-
Building on Windows
76
-
-------------------
77
-
78
-
A Visual Studio project file can be found in the "vcnet" directory. You'll
79
-
need the following minimum software:
112
+
Packaging
113
+
---------
80
114
81
-
- Visual Studio 2017 Community Edition
82
-
- Advanced Installer 15.4
83
-
- Windows SDK 10.0.17763.0
115
+
On Linux run:
84
116
85
-
Open the "ippeveselfcert.sln" file and then build the installer target.
117
+
make dist
86
118
119
+
A tar.gz file will be placed in the current directory.
87
120
88
-
Getting Debug Logging
89
-
---------------------
121
+
On macOS you'll need the PWG code signing certificate (available from the PWG officers for official use only) or your own certificate loaded into your login keychain. Then run:
90
122
91
-
The following environment variables are used to enable and control debug
92
-
logging:
123
+
CODESIGN_IDENTITY="common name or SHA-1 hash of certificate" make dist
93
124
94
-
-`CUPS_DEBUG_FILTER`: Specifies a POSIX regular expression to control which
95
-
messages are logged.
96
-
-`CUPS_DEBUG_LEVEL`: Specifies a number from 0 to 9 to control the verbosity of
97
-
the logging. The default level is 1.
98
-
-`CUPS_DEBUG_LOG`: Specifies a log file to use. Specify the name "-" to send
99
-
the messages to stderr. Prefix a filename with "+" to append to an existing
100
-
file. You can include a single "%d" in the filename to embed the current
101
-
process ID.
125
+
On Windows just build the installer target in Visual Studio - you'll find the
0 commit comments