Porting to OS/2: Install compress utils(tar, gzip, bzip, xz) and make
Other than zip, unix world prefer the combination of archiver(tar) and compressor(gzip, bzip, xz).
Those utils are also available on OS/2.
Unzip and copy tar.exe to x:\usr\bin.
To untar, use 'tar xvf filename'. Usually, filename has .tar as a extension.
This zip includes gzip124-32.zip. Unzip it and copy gzip.exe to x:\usr\bin
To extract with tar, use 'tar xvzf filename'. Usually, filename has .tar.gz or .tgz as a extension.
Unzip and copy BZIP2 directories to x:\usr with preserving its directory structures. And move x:\usr\bin\bz2.dll to x:\usr\dll
To extract with tar, use 'tar xvjf filename'. Usually, filename has .tar.bz2 as a extension.
// ----- 2016/01/04
You can get newer versions of bzip2 from hobbes.
// -----
Unzip and copy XZ directories to x:\usr. And move x:\usr\bin\lzma.dll to x:\usr\dll.
To extract with tar, use 'tar xvJf filename'. Usually, filename has .tar.xz as a extension.
// ----- 2016/01/04
You can get newer versions of xz from hobbes.
// -----
To help build of complicated projects, make is required. Let's prepare this, as well.
Copy make.exe x:\usr\bin.
BTW, many makefiles expect that its shell is /bin/sh. So you'd better call make with SHELL=/bin/sh. But this is uncomfortable. Then ? Let's use a scripts for this. ^^
Create gmake.cmd in x:\usr\bin. Whenever you run this script, the output is stored in build.log in a directory where it was run.
However, if you use makefiles using OS/2 commands, then just use make than gmake.cmd. Qt project itself and many Qt programs are good examples.
Those utils are also available on OS/2.
tar
Unzip and copy tar.exe to x:\usr\bin.
To untar, use 'tar xvf filename'. Usually, filename has .tar as a extension.
gzip
This zip includes gzip124-32.zip. Unzip it and copy gzip.exe to x:\usr\bin
To extract with tar, use 'tar xvzf filename'. Usually, filename has .tar.gz or .tgz as a extension.
bzip2
Unzip and copy BZIP2 directories to x:\usr with preserving its directory structures. And move x:\usr\bin\bz2.dll to x:\usr\dll
- unzip bzip2-1.0.6.zip
- xcopy /s/e/v/h/t/r BZIP2 x:\usr
- move x:\usr\bin\bz2.dll x:\usr\dll
To extract with tar, use 'tar xvjf filename'. Usually, filename has .tar.bz2 as a extension.
// ----- 2016/01/04
You can get newer versions of bzip2 from hobbes.
// -----
xz
Unzip and copy XZ directories to x:\usr. And move x:\usr\bin\lzma.dll to x:\usr\dll.
- unzip xz-5.0.5.zip
- xcopy /s/e/v/h/t/r XZ x:\usr
- move x:\usr\bin\lzma.dll x:\usr\dll
To extract with tar, use 'tar xvJf filename'. Usually, filename has .tar.xz as a extension.
// ----- 2016/01/04
You can get newer versions of xz from hobbes.
// -----
To help build of complicated projects, make is required. Let's prepare this, as well.
make
Copy make.exe x:\usr\bin.
BTW, many makefiles expect that its shell is /bin/sh. So you'd better call make with SHELL=/bin/sh. But this is uncomfortable. Then ? Let's use a scripts for this. ^^
| 1 2 3 4 5 6 7 8 9 10 11 | /* gmake.cmd */ parse arg argall '@echo off' 'setlocal' 'set LANG=C' 'set COMSPEC=/bin/sh' 'set MAKESHELL=/bin/sh' 'make' argall '2>&1 | tee build.log' ec = rc 'endlocal' exit ec |
Create gmake.cmd in x:\usr\bin. Whenever you run this script, the output is stored in build.log in a directory where it was run.
However, if you use makefiles using OS/2 commands, then just use make than gmake.cmd. Qt project itself and many Qt programs are good examples.
댓글
댓글 쓰기