Rev 46 | Blame | Compare with Previous | Last modification | View Log | Download | RSS feed
# IFS Tool for QNX
![QNX 8.0 x86_64 UEFI booting an IFS created with mkifs](filedetails.php?repname=QNX%208.QNX8%20IFS%20tool&path=%2Fx86-uefi-console.png "QNX 8.0 x86_64 UEFI booting an IFS created with mkifs")
__ifstool__ is a portable open-source reimplementation of [QNX 8.0's mkifs](https://www.qnx.com/developers/docs/8.0/com.qnx.doc.neutrino.utilities/topic/m/mkifs.html), that is able to pack, unpack and analyze x86_64 BIOS and UEFI QNX IFS images, compressed or not, bootable or not, using the same script file-based syntax as mkifs. Most of the mkifs options are supported. Can be built as a **native QNX tool**. Already used in production in some places.
As an illustration, the bootable QNX8 IFS pictured in the above screenshot was built using __ifstool__.
The goal was to turn QNX8 into a self-hosted platform. Since QNX no longer supplies a native toolchain (compiler, linker, binary utilities, IFS utilities) __ifstool__, when used along with the GNU linker (cf. [QNX8 GNU binutils](listing.php?repname=QNX%208.QNX8%20GNU%20binutils)) can be used as a drop-in replacement.
## Language
POSIX-compliant ANSI C99.
## IDE
The development environment used was [Microsoft Visual Studio](https://visualstudio.microsoft.com). A Visual Studio 2022 solution file is supplied.
## Dependencies
* Oberhumer's [miniLZO](https://www.oberhumer.com/opensource/lzo/#minilzo) compression library (supplied)
* Oberhumer's [UCL](https://www.oberhumer.com/opensource/ucl/) compression library (supplied)
## How to build
* For __Win32__: open Visual Studio project -> Build.
* For __QNX8/x86-64__: run `make.cmd` (if using Win32) or `make.sh` (if using a POSIX platform).
* For __QNX8/aarch64le__: run `make.cmd` (if using Win32) or `make.sh` (if using a POSIX platform). Note the bootable IFS feature on this target is untested.
* For __GNU/Linux__: run `make.sh`
* For __FreeBSD__: run `make.sh`
* For __macOS/Darwin__: run `make.sh` -- yes, it works on macOS too :)
Feedback is welcome.
--
Pierre-Marie Baty <pm@pmbaty.com>