How to Install and Uninstall libMagick++-devel Package on openSuSE Tumbleweed

Last updated: October 05,2024

1. Install "libMagick++-devel" package

In this section, we are going to explain the necessary steps to install libMagick++-devel on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                libMagick++-devel
            
                    
    
    Copied

2. Uninstall "libMagick++-devel" package

This guide covers the steps necessary to uninstall libMagick++-devel on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                libMagick++-devel
            
                    
    
    Copied

3. Information about the libMagick++-devel package on openSuSE Tumbleweed

Information for package libMagick++-devel:
------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libMagick++-devel
Version : 7.1.1.29-3.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 424.2 KiB
Installed : No
Status : not installed
Source package : ImageMagick-7.1.1.29-3.1.src
Upstream URL : https://imagemagick.org/
Summary : Development files for ImageMagick's C++ interface
Description :
This is Magick++, the object-oriented C++ API for the ImageMagick
image-processing library.
Magick++ supports an object model inspired by PerlMagick. Magick++
should be faster than PerlMagick since it is written in a compiled
language which is not parsed at run-time. This makes it suitable for
Web CGI programs. Images support implicit reference counting so that
copy constructors and assignment incur almost no cost. The cost of
actually copying an image (if necessary) is done just before
modification and this copy is managed automatically by Magick++.
De-referenced copies are automatically deleted. The image objects
support value (rather than pointer) semantics so it is trivial to
support multiple generations of an image in memory at one time.