QB64 FAQ
As with everything else, this list will be updated to correspond to new progress of QB64 so make sure that you are using the latest version of QB64. Please note that it may take a short time to update this list.
Q: What is QB64?
A: QB64 is a BASIC compatible Editor and C++ emitter that creates working Executable files from QBasic BAS files that can be run on 32 or 64 bit PC's using Windows (XP to 10), Linux or macOS. The goal is to be 100% compatible with QuickBASIC 4.5 plus add hundreds of new abilities such as program icons and custom sized windows and a great retro Editor with builtin help.
The new keywords add some new features such as playing music or sound files and instant access to 32 bit graphics file images. Also TCP/IP internet communication is available to download files, email messages over the web or play internet games. DLL Libraries can add more programming options and QB64 can access all of the new USB gaming controllers and printers.
QB is an abbreviation for QBasic or QuickBASIC which is an easy to learn language that grew very popular in the 90's. It uses simple syntax but holds great potential as there are methods to achieve nearly anything. QBasic is more alive than ever with QB64!
Keywords currently not supported by QB64
Q: Does it have modern features? Do they HAVE to be used?
A: QB64 has plenty of modern features, but they do not have to be used. You may just want to run some of your old favorites.
You could code using the original QuickBASIC syntax all the way through and it should work as you expect it to or even better. QB64 is often faster and has none of the memory limitations that plagued QBasic in the past.
QB64 is not meant to run PDS (7.1) QBX code. Most GW Basic code will run with minor changes.
The modern statements are designed to go along with the BASIC philosophy and expand QBasic into the future!
1) Full graphic functions for images up to 32 bit color. Alpha transparency supported. 2) Instant loading of image files including BMP, PNG, JPEG, GIF and more... 3) Supports stereo sound files like WAV, OGG, MP3, speaker and volume control and more... 4) Animation is easy to do using _DISPLAY instead of page flipping, to achieve flicker-free graphics. 5) Clipboard reading and writing support. 6) Networking over TCP/IP and Email. 7) True type font and Unicode support for many Languages. 8) Integrated mouse and game controller input including scroll wheel support. 9) Support for C++, OpenGL, Windows API and other custom Dynamic Link Libraries. |
Q: How do I install QB64 on Windows, Linux, macOS?
A: QB64 supports the following Operating Systems:
- 1) Download the appropriate package according to your system from GitHub
- 2) Unpack the contents to any location on your computer. Avoid unpacking to Program Files or other system folders that may require administrative privileges. QB64 needs to have full write permissions to its own folder.
- Executable programs are portable between like systems by copying the stand-alone executable file.
- 1) Download the appropriate package according to your system from GitHub
- 2) After extracting the downloaded package, run the installation batch/script called ./setup_lnx.sh in the main qb64 folder to setup QB64.
- 3) Most dependencies should be automatically downloaded by the setup script, but these are the ones you should look for if compilation fails: OpenGL developement libraries, ALSA development libraries, GNU C++ Compiler (g++)
- 1) You must install Apple's Xcode command line tools for C++ compilation from their website. The simplest way to do so is opening a terminal window and typing the following command: xcode-select --install (more info here: Xcode download)
- (you won't be using the Xcode interface, QB64 just needs to have access to the C++ compiler and libraries it installs)
- 3) Download the appropriate package according to your system from GitHub
- Extract the downloaded package and run ./setup_osx.command, found within the QB64 folder to install the QB64 compiler.
- Executable programs are portable between macOS systems by copying the executable file.
- To help launch executables without a console, a file called programname_start.command is created along with the program.
Q: Why won't QB64 work on my computer?
QB64 currently supports Windows versions from XP to the latest version. Most Linux and macOS versions are also supported.
- Don't move QB64 executable out of the QB64 folder. The various sub-folders hold the C++ compiler files and libraries.
- QB64 does not change any settings on your machine. All required files are in the QB64 folder.
Q: Are there any known incompatibilities?
A: There are some things that QB64 cannot do, like direct hardware access, which makes older more advanced programs that make use of ABSOLUTE, INTERRUPT, PEEK, POKE and OUT not work properly. Although some older functionality is emulated, if your program doesn't use such statements you probably won't notice any difference between QB 4.5 and QB64 (and if you do, report it as a bug in the forums). You can expect the most common addresses for interrupts, etc. to be functioning.
See: Keywords currently not supported by QB64
You should be careful with CPU usage. QB64 is a lot faster than QBasic was and it does not have many of the size limitations that confined QBasic programming abilities. Having said that, care must be taken to assure that programs do not hog resources. To do that, use speed limits when possible to keep the resources used to a minimum. Also, Monitor Task Manager when your programs are running, as it can tell you how much or system resources are being used in different parts of a program. The following keywords can lower the impact of your programs on those resources by releasing them to other programs:
- _LIMIT: Limits the loops per second in any loop and thus lowers the overall CPU usage.
- _DELAY: Pauses a procedure and releases unused resources for other programs.
- SLEEP: Stops or delays program procedures and shares resources.
QB64 can be fast when you need it to be, but take the time to consider the impact of your program on other programs as people seldom have only one program running and the OS has tasks it must do too.
Q: How do I update the information in QB64's help system?
A: The help provided in the QB64 IDE Help System fetches the pages from this wiki. Use the Update current page in the IDE Help menu selection to update a page. Use the Update all pages choice to update them all, but this may take longer.
Q: Can I use the same libraries with QB64 that I used with QB 4.5?
A: If the libraries are pure QB 4.5 code then yes, otherwise no. QLB files are not supported but you can easily copy your favorite SUBs or FUNCTIONs to a text BI file and $INCLUDE them at the end of any program. Include them after all SUB and FUNCTION code in the BAS file.
DECLARE LIBRARY allows users to reference C, Windows, OpenGL and other DLL libraries. If you find some functions that you like please share them with us at the forum! The following pages list working functions our members have found and tested:
Q: I can't get my QB 4.5 source code to work in QB64! Why?
A: QB64 is 99% compatible with QB4.5 programs. The commands that haven't been implemented are either obsolete or are too obscure and have been replaced by modern functionality.
See: Keywords currently not supported by QB64
Q: What files are required to run my QB64 compiled program in my Operating System?
A: Programs compiled by QB64 (version 1.000 and up) are stand-alone so no external files are required to be with your program's EXE file.
Q: Is there a way to use the compiler without running my program or using the IDE?
A: Yes! Just type QB64 -? at the command prompt to see a list of available options.
- Note
- The -c and -x option do just compile a program without running it.
- The -z option does not even create an executable file, it makes only the first pass of compiling (syntax checking and generate C code).
Usage: qb64 [switches] <file>
Options:
<file> Source file to load
-c Compile instead of edit
-o <output file> Write output executable to <output file>
-x Compile instead of edit and output the result to the
console
-w Show warnings
-q Quiet mode (does not inhibit warnings or errors)
-m Do not colorize compiler output (monochrome mode)
-e Enable OPTION _EXPLICIT, making variable declaration
mandatory (per-compilation; doesn't affect the
source file or global settings)
-s[:switch=true/false] View/edit compiler settings
-l:<line number> Start the IDE at the specified line number
-p Purge all pre-compiled content first
-z Generate C code without compiling to executable
|