The Orthanc build from source code uses a standard CMake build routine. This is a little different than a standard Make, but not difficult.
Displaying CMAKE options
CMAKE is configured through the CMakeLists.txt file supplied with the Orthanc source code. To display the available options, and their setting, run the command cmake -LAH
Compressed JPEG images
Compressed JPEG (JPEG 2000) images rely upon the JPEG decoding of DCMTK. If compressed JPEG images are not being displayed, check the output from cmake -LAH that includes the string jpeg. Missing DCMTK libraries may be listed here.
CMAKE error about libuuid
See this post. Basically, install uuid-dev (or uuid-devel), delete and re-create the orthanc-build directory, and repeat the cmake command.
Add the fully defined path of each Lua script to the array LuaScripts in the configuration file.
If you implement access control by the Lua function IncomingHttpRequestFilter (described on the Orthanc Wiki) under 'Filtering Incoming REST Requests', file uploads will be prompted for a username and password, even if the configuration option RemoteAccessAllowed is set to true.
To enable file upload through the web interface other than from localhost, edit the configuration entry RemoteAccessAllowed .
HTTP Basic authentication can be provided through a curl command using
curl --user name:password <url>
Orthanc plugins are built using cmake. To install plugins, they must be included in the Orthanc configuration file, either individually or as the name of a directory that will contain all plugins. In this Linux example, the Plugins directory (within the Orthanc main directory) contains multiple compiled plugins.
$ ls Plugins/*.so | more Plugins/libDwvOrthancPlugin.so Plugins/libOrthancDicomWeb.so Plugins/libOrthancWebViewer.so
This directory is included in the Orthanc configuration file.
"Plugins" : [ "./Plugins" ],