From QB64 Wiki

Jump to: navigation, search

The DECLARE LIBRARY declaration allows the use of external library SUB and FUNCTION procedures supported by QB64.



DECLARE [DYNAMIC|CUSTOMTYPE|STATIC] LIBRARY [{"Library_filename"|"Headerfile"}]
{SUB|FUNCTION} [procedure_name ALIAS] library_procedure ([BYVAL] parameter AS, ...)
. 'other SUBs or Functions as required


  • The Library_filename is needed if a Library is not already loaded by QB64. Do not include the .DLL, LIB or .H file extension.
    • It's always a good idea to try declaring Windows API libraries without a Library_filename first, as most Windows headers are already included in QB64 source.
  • Begin the Library_filename with ./ or .\ to make it relative to the path where your source file is saved, so you can keep all your project files together.
  • Procedure_name is any program procedure name you want to designate by using ALIAS with the Library_procedure name.
  • Library procedure is the actual procedure name used inside of the library or header file.

Library Types

  • DYNAMIC links a program to functions in dynamically linkable libraries. At present, only .DLL files are supported
  • CUSTOMTYPE is already implied when using DECLARE DYNAMIC LIBRARY. This type of library just allows the same flexibility to apply when referencing STATIC libraries that are used to refer to dynamic libraries. Supports shared object (*.so) libraries.
  • STATIC is the same as DECLARE LIBRARY except that it prioritizes linking to static libraries (*.a/*.o) over shared object (*.so) libraries, if both exist. As Windows doesn't use shared libraries (DLLs are different) this does not affect Windows users.


  • The declaration can be used with C++ sub-procedures, Windows API and QB64 SDL (versions prior to 1.000)/OpenGL (version 1.000 and up) Libraries.
  • Library filenames can be listed to combine more than one DLL or Header file name or path into one DECLARE LIBRARY block.
  • C procedures can use a header file name. File code must be included with program code. Do not include the .h extension.
  • Parameters used by the Library procedure must be passed by value (BYVAL) except for STRING characters.
  • When using a procedure from an unsupported Dynamic Link Library (DLL file) use DECLARE DYNAMIC LIBRARY.
  • The _OFFSET in memory can be used in CUSTOMTYPE, STATIC and DYNAMIC LIBRARY declarations.
  • Declarations can be made inside of SUB or FUNCTION procedures. Declarations do not need to be at program start.
  • NOTE: It is up to the user to document and determine the suitability of all Libraries and procedures they choose to use! QB64 cannot guarantee that any procedure will work and cannot quarantee any troubleshooting help.


Example 1: Using an SDL library procedure as a program SUB procedure to move the mouse pointer to a coordinate (works in versions prior to 1.000):

DECLARE LIBRARY SUB SDL_WarpMouse (BYVAL column AS LONG, BYVAL row AS LONG) 'SDL procedure name END DECLARE SCREEN _NEWIMAGE(640, 480, 256) 'simulate screen 12 with 256 colors RANDOMIZE TIMER DO _DELAY 1 x = RND * 640: y = RND * 480 LINE (x, y)-STEP(10, 10), RND * 100 + 32, BF MouseMove x + 5, y + 5 LOOP UNTIL LEN(INKEY$) 'any keypress quits END SUB MouseMove (x AS LONG, y AS LONG) SDL_WarpMouse x, y 'call SDL library procedure END SUB

Code by Galleon
Explanation: The SDL Library is included and loaded with QB64 versions prior to 1.000, so these procedures are directly available for use.
Using ALIAS to create a program SUB or FUNCTION using QB64 SDL ONLY

SCREEN 12 DECLARE LIBRARY SUB MouseMove ALIAS SDL_WarpMouse (BYVAL column&, BYVAL row&) END DECLARE _DELAY 2 MouseMove 100, 100 _DELAY 2 MouseMove 200, 200

Explanation: When a Library procedure is used to represent another procedure name use ALIAS instead. Saves creating a SUB!

Example 2: Don't know if a C function is defined by C++ or QB64? Try using empty quotes.


Explanation: The C function 'addone' exists in a library QB64 already links to, but it hasn't been defined as a C function or a QB64 function. By using "" we are telling QB64 the function exists in a library which is already linked to and that it must define the C function before calling it, as well as allowing QB64 code to call it. Trying the above code without the "" will fail.
Note: What libraries are or aren't automatically used in the linking process is not formally defined, nor is it guaranteed to stay that way in future versions of QB64.

Example 3: For this next example, download the file 'add.lib' and place it in you QB64 folder:


Explanation: Here, we tell QB64 to link to add.lib (QB64 searches for add.lib, add.a, and add.o in that order and uses the first that it finds). The function addtwo exists inside the library file add.lib but isn't defined anywhere else. QB64 creates the C definition for the function addtwo so that it can be called from our QB64 code.
Note: If the C function definition auto-created by QB64 does not exactly match the definition in the library file, it will not work. As a result of this it is often better to provide the C function definitions in the form of a C header file, such as in the following example.

Example 4: NTport is a commercial library hosted at, but it does provide an evaluation version (it has a 3 second wait pop-up window) which we will use here. You don't need to download NTport, just download the following 3 files and put them in your QB64 folder:

NTport.lib            NTport.h               Ntport.dll
IMPORTANT: The DLL is loaded automatically by the static library, we are not linking directly to the DLL, we are static linking (NOT directly or dynamically linking). This is an important concept to understand!

DECLARE LIBRARY "ntport" FUNCTION GetLPTPortAddress% (BYVAL PortNo%) END DECLARE PRINT "&H" + HEX$(GetLPTPortAddress%(1))

Explanation: DECLARE LIBRARY also searches for C header files with a .h extension. So in this case it is using the header ntport.h and linking with ntport.lib just by specifying "NTPORT". The C function definitions are stored in ntport.h so even if our QB64 functions don't exactly match (eg. LONG instead of INTEGER) it will still work.
If you look inside 'ntport.h' you'll find the following line containing the C function definition of the command we used:


Galleon's OpenGL Library with demo program download:

QB64 version 1.000 and up produce standalone executables. External DLL files must be distributed with your program.
Note: QB64 versions prior to 1.000 require all default DLL files to either be with the program or in the C:\WINDOWS\SYSTEM32 folder.

See also:

Go to Keyword Reference - Alphabetical
Go to Keyword Reference - By usage
Go to Main WIKI Page
Personal tools