How to Install and Uninstall libsqlitecpp-dev Package on Kali Linux

Last updated: May 20,2024

1. Install "libsqlitecpp-dev" package

This is a short guide on how to install libsqlitecpp-dev on Kali Linux


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                libsqlitecpp-dev
            
                    
    
    Copied

2. Uninstall "libsqlitecpp-dev" package

Please follow the guidance below to uninstall libsqlitecpp-dev on Kali Linux:


    
        
            $
        

        
            
                sudo apt remove
            
                        
                libsqlitecpp-dev
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the libsqlitecpp-dev package on Kali Linux

Package: libsqlitecpp-dev
Source: sqlitecpp (3.3.1-1)
Version: 3.3.1-1+b1
Installed-Size: 276
Maintainer: Debian QA Group
Architecture: amd64
Depends: libsqlite3-dev (>= 3.7.15)
Size: 56632
SHA256: 2073f7f3a2b6e414655e7d7d3b81e5618fd7b225e6e1eb35d8fbeb57739b3340
SHA1: b51d6e2084b9aa82e8d6034ba08c5171a12af611
MD5sum: 9a61fd1912d275fb63c75621cd7f2953
Description: smart and easy to use C++ SQLite3 wrapper
SQLiteC++ offers an encapsulation around the native C APIs of SQLite, with a
few intuitive and well documented C++ classes.
.
The goals of SQLiteC++ are:
- to offer the best of the existing simple C++ SQLite wrappers
- to be elegantly written with good C++ design, STL, exceptions and RAII idiom
- to keep dependencies to a minimum (STL and SQLite3)
- to be portable
- to be light and fast
- to be thread-safe only as much as SQLite “Multi-thread” mode (see below)
- to have a good unit test coverage
- to use API names sticking with those of the SQLite library
- to be well documented with Doxygen tags, and with some good examples
- to be well maintained
Description-md5:
Multi-Arch: same
Homepage: https://srombauts.github.io/SQLiteCpp/
Tag: devel::library, role::devel-lib
Section: libdevel
Priority: optional
Filename: pool/main/s/sqlitecpp/libsqlitecpp-dev_3.3.1-1+b1_amd64.deb