I have a user in a group: 'demo'. I wanna set the policy that this users just can run 10 commands, like 'vim','nano','cd' and etc. Or, set the policy to have access. How To Install Gprof On Ubuntu Phone. Shared libraries with GCC on Linux By anduril. Libraries are an. Compiled and ready for you to use. They often provide generic functionality, like linked lists or binary trees that can hold any data, or specific functionality like an interface to a database server such as My.

GraphicsMagick is distributed in a number of different archive formats. The source code must be extracted prior to compilation as follows: 7z 7-Zip archive format. The Z-Zip format may be extracted under Unix using '7za' from the P7ZIP package (). Extract similar to: 7za x GraphicsMagick-1.3.7z.tar.bz2 BZip2 compressed tar archive format. Requires that both the bzip2 () and tar programs to be available. Extract similar to: bzip2 -d GraphicsMagick-1.3.tar.bz tar -xvf -.tar.gz Gzip compressed tar archive format. Requires that both the gzip () and tar programs to be available.

Extract similar to: gzip -d GraphicsMagick-1.3.tar.gz tar -xvf -.tar.lz Lzip compressed tar archive format. Requires that both the lzip () and tar programs to be available. Extract similar to: lzip -d -c GraphicsMagick-1.3.tar.gz tar -xvf -.tar.xz LZMA compressed tar archive format. Requires that LZMA utils () and tar programs to be available. Extract similar to: xz -d GraphicsMagick-1.3.tar.xz tar -xvf - zip PK-ZIP archive format. Requires that the unzip program from Info-Zip () be available.

Extract similar to: unzip GraphicsMagick-1.3.zip The GraphicsMagick source code is extracted into a subdirectory similar to 'GraphicsMagick-1.3'. After the source code extracted, change to the new directory (using the actual directory name) using a command similar to: cd GraphicsMagick-1.3. GraphicsMagick may be built under the Windows '95-XP Cygwin Unix-emulation environment available for free from It is suggested that the X11R6 package be installed since this enables GraphicsMagick's X11 support (animate, display, and import sub-commands will work) and it includes the Freetype v2 DLL required to support TrueType and Postscript Type 1 fonts. Make sure that /usr/X11R6/bin is in your PATH prior to running configure.

If you are using Cygwin version 1.3.9 or later, you may specify the configure option '--enable-shared' to build Cygwin DLLs. Drivers Ed Book Caroline B Cooney Summary. Specifying '--enable-shared' is required if you want to build PerlMagick under Cygwin because Cygwin does not provide the libperl.a static library required to create a static PerlMagick.

Note that older Cygwin compilers may not generate code which supports reliably catching C++ exceptions thrown by DLL code. The Magick++ library requires that it be possible to catch C++ exceptions thrown from DLLs.

The test suite make check includes several tests to verify that C++ exceptions are working properly. GraphicsMagick may be built using the free MinGW ('Minimalistic GNU for Windows') package, available from or from which consist of GNU-based (GCC) compilation toolsets plus headers and libraries required to build programs which are entirely based on standard Microsoft Windows DLLs so that they may be used for proprietary applications. MSYS provides a Unix-style console shell window with sufficient functionality to run the GraphicsMagick configure script and execute 'make', 'make check', and 'make install'. GraphicsMagick may be executed from the MSYS shell, but since it is a normal Windows application, it will work just as well from the Windows command line.

Unlike the Cygwin build which creates programs based on a Unix-emulation DLL, and which uses Unix-style paths to access Windows files, the MinGW build creates native Windows console applications similar to the Visual C++ build. Run-time performance is similar to the Microsoft compilers. The base MinGW (or MinGW-w64) package and the MSYS package should be installed. Other MinGW packages are entirely optional. Once MSYS is installed a MSYS icon (blue capital 'M') is added to the desktop.

Double clicking on this icon starts an instance of the MSYS shell. Start the MSYS console and follow the Unix configure and build instructions. The configure and build for MinGW is the same as for Unix. Any additional delegate libraries (e.g. Libpng) will need to be built under MinGW in order to be used.

These libraries should be built and installed prior to configuring GraphicsMagick. While some delegate libraries are easy to configure and build under MinGW, others may be quite a challenge. Lucky for us, the most common delegate libraries are available pre-built, as part of the GnuWin32 project, from The relevant packages are bzip2, freetype, jbigkit, libintl, jpeg, libpng, libtiff, libwmf and zlib. However, note that for freetype to be detected by configure, you must move the freetype directory out of GnuWin32 include freetype2 and into GnuWin32 include. Note that older MinGW compilers may not generate code which supports reliably catching C++ exceptions thrown by DLL code. The Magick++ library requires that it be possible to catch C++ exceptions thrown from DLLs. The test suite ( make check) includes several tests to verify that C++ exceptions are working properly.

If the MinGW you are using fails the C++ exception tests, then the solution is to either find a MinGW with working C++ exceptions, configure a static build with --disable-shared, or disable building Magick++ with --without-magick-plus-plus. Note that the default installation prefix is MSYS's notion of /usr/local which installs the package into a MSYS directory. To install outside of the MSYS directory tree, you may specify an installation prefix like /c/GraphicsMagick which causes the package to be installed under the Windows directory C: GraphicsMagick. The installation directory structure will look very much like the Unix installation layout (e.g. C: GraphicsMagick bin, C: GraphicsMagick lib, C: GraphicsMagick share, etc.). Paths which may be embedded in libraries and configuration files are transformed into Windows paths so they don't depend on MSYS. Given a modern and working MinGW32 or mingw-w64 installation, it is easy to cross-compile GraphicsMagick from a Unix-type host to produce Microsoft Windows executables.

While configure is designed to ease installation of GraphicsMagick, it often discovers problems that would otherwise be encountered later when compiling GraphicsMagick. The configure script tests for headers and libraries by executing the compiler (CC) with the specified compilation flags (CFLAGS), pre-processor flags (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged to the file 'config.log'. If configure fails to discover a header or library please review this log file to determine why, however, please be aware that errors in the config.log are normal because configure works by trying something and seeing if it fails. An error in config.log is only a problem if the test should have passed on your system. After taking corrective action, be sure to remove the 'config.cache' file before running configure so that configure will re-inspect the environment rather than using cached values. Common causes of configure failures are: • A delegate header is not in the header include path (CPPFLAGS -I option).

• A delegate library is not in the linker search/run path (LDFLAGS -L/-R option). • A delegate library is missing a function (old version?).OB • The compilation environment is faulty. If all reasonable corrective actions have been tried and the problem appears to be due to a flaw in the configure script, please send a bug report to the configure script maintainer (currently ). All bug reports should contain the operating system type (as reported by 'uname -a') and the compiler/compiler-version. A copy of the configure script output and/or the config.log file may be valuable in order to find the problem. If you send a config.log, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.

Once GraphicsMagick is configured, these standard build targets are available from the generated Makefiles: 'make' Build the package 'make install' Install the package 'make check' Run tests using the uninstalled software. On some systems, 'make install' must be done before the test suite will work but usually the software can be tested prior to installation.

'make clean' Remove everything in the build directory created by 'make' 'make distclean' Remove everything in the build directory created by 'configure' and 'make'. This is useful if you want to start over from scratch. 'make uninstall' Remove all files from the system which are (or would be) installed by 'make install' using the current configuration. Note that this target does not work for PerlMagick since Perl no longer supports an 'uninstall' target. To confirm your installation of the GraphicsMagick distribution was successful, ensure that the installation directory is in your executable search path and type gm display The GraphicsMagick logo should be displayed on your X11 display.

On this page • • • There's no doubt that testing is an integral and one of the most important aspects of the software development process. And by testing, we don't mean just testing the code for bugs - of course, bug detection is important as nobody would want their software to be buggy - performance of the code also equally matters these days. If broken down to the last bit, performance testing effectively tests how much time a particular piece of code - say a function - is consuming. As is usually the case, a function or a group of functions may correspond to one of the many features of a software. So, if through performance testing, we can enhance the performance of these functions in code, the overall performance of the software becomes better.