libjpeg<\/a> is the Independent JPEG Group’s (IJG) widely used free library for JPEG image compression.<\/p>\n There are no restrictions on access to the libjpeg installation on the CSF. All usage must adhere to this license restrictions listed under the “Legal Issues” section of the We now recommend loading modulefiles within your jobscript so that you have a full record of how the job was run. See the example jobscript below for how to do this. Alternatively, you may load modulefiles on the login node and let the job inherit these settings<\/abbr>.<\/p>\n Load one<\/strong> of the following modulefiles to set up your environment:<\/p>\n You will mostly use the libjpeg installation on CSF3 when compiling your own software. This allows you to add libjpeg functionality to your own apps. There are some tools you can also run to process existing image files (see below).<\/p>\n The modulefiles will set an environment variable named An example compilation command could be<\/p>\n The modulefiles also set the following environment variables which can help compilers and build tools find the header and library files automatically: You must load the libjpeg modulefile before running your PROJ-capable application (unless you have statically linked your code against the PROJ libraries). The modulefile will set the Please do not run libjpeg-capable applications on the login node. Jobs should be submitted to the compute nodes via batch.<\/p>\n Create a batch submission script (which will load the modulefile in the jobscript), for example:<\/p>\n Submit the jobscript using: <\/p>\n where scriptname<\/em> is the name of your jobscript.<\/p>\n The PROJ See the JPEG Clubs’s website for documentation<\/a>.<\/p>\n None.<\/p>\n","protected":false},"excerpt":{"rendered":" Overview libjpeg is the Independent JPEG Group’s (IJG) widely used free library for JPEG image compression. There are no restrictions on access to the libjpeg installation on the CSF. All usage must adhere to this license restrictions listed under the “Legal Issues” section of the $LIBJPEGDIR\/README file in the installation. Set up procedure We now recommend loading modulefiles within your jobscript so that you have a full record of how the job was run. See.. Read more »<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"parent":140,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-7278","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/7278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/comments?post=7278"}],"version-history":[{"count":3,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/7278\/revisions"}],"predecessor-version":[{"id":7283,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/7278\/revisions\/7283"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/pages\/140"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/csf3\/wp-json\/wp\/v2\/media?parent=7278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}$LIBJPEGDIR\/README<\/code> file in the installation.<\/p>\nSet up procedure<\/h2>\n
\r\n# Load one<\/strong> of the following modulefiles\r\nmodule load libs\/gcc\/libjpeg\/9e\r\nmodule load libs\/gcc\/libjpeg\/8d\r\n<\/pre>\n
Compiling a libjpeg-capable application<\/h2>\n
${LIBJPEGDIR}<\/code> which can then be used in your compilation process (e.g., in a Makefile or directly on the command-line) to access the header and library files:<\/p>\n\n
gcc -I${LIBJPEGDIR}\/include ....<\/pre>\n<\/li>\ngcc ... -L${LIBJPEGDIR}\/lib -lproj<\/pre>\n<\/li>\n${PROJDIR}<\/code> rather than $LIBJPEGDIR<\/code>.<\/li>\n<\/ul>\n\r\ngcc -I${LIBJPEGDIR}\/include example_jpeg.c -o example_jepg -L${LIBJPEGDIR}\/lib -ljpeg\r\n<\/pre>\nPKG_CONFIG_PATH<\/code>, C_INCLUDE_PATH<\/code>, CPATH<\/code> and LIBRARY_PATH<\/code>.<\/p>\nRunning an libjpeg-capable application<\/h2>\n
LD_LIBRARY_PATH<\/code> variable to allow executables to find the share libraries at runtime.<\/p>\nSerial batch job submission<\/h3>\n
\r\n#!\/bin\/bash --login\r\n#$ -cwd # Job will run from the current directory\r\n # NO -V line - we load modulefiles in the jobscript\r\n\r\n# Load the version you require\r\nmodule load libs\/gcc\/libjpeg\/9e\r\n\r\n# Run my application I compiled earlier\r\n.\/myjpegapp<\/em> arg1<\/em> ...\r\n<\/pre>\n
qsub scriptname<\/em><\/pre>\n
libjpeg Tools<\/h3>\n
bin<\/code> directory is added to your path so that you can access the ...jpeg<\/code> tools. Use ls ${LIBJPEGBIN}<\/code> to see all binary tools:<\/p>\n\r\n# libjpeg tools - must be used in batch jobs, as above\r\ncjpeg djpeg jpegtran rdjpgcom wrjpgcom\r\n<\/pre>\n
Further info<\/h2>\n
Updates<\/h2>\n