Setup of kos32-gcc
Posted: Tue Sep 18, 2018 12:04 am
Dear all. I found: https://github.com/callcc/KolibriOS/blo ... /build.txt
For GCC it reads:
* For a GCC program, get the toolchain at
http://ftp.kolibrios.org/users/Serge/new/Toolchain/.
Under Windows, you need the package with "msys" in name and MinGW;
after installing MinGW, unpack the package to
\MinGW\msys\1.0\home\autobuild\tools\win32, the package assumes
exactly this path. Run MinGW shell.
Under Linux, you need the package with "linux" in name
and runtime library cloog; e.g. for Debian-based distributives
use apt-get install libcloog-isl4. Unpack the package to
/home/autobuild/tools/win32, the package assumes exactly this path.
In both MinGW and Linux, make sure that the command
/home/autobuild/tools/win32/bin/kos32-gcc
invokes the compiler.
If the program uses libraries, you will also need to either compile
them separately or download SDK, if they are included to SDK.
Compiling is ultimately a sequence of calls to kos32-gcc and kos32-ld,
but filling exact parameters can be tricky, so maybe you want to
use Tup - proceed to Q2/A2 - or Make, if a maintainer has provided
Makefile.
---
I have untared as described to /home/autobuild/tools/win32.
Where exactly to I unpack the SDK available also at same link/location mentioned in the build.txt? This important information is not mentioned in the text.
Where can one download a test package (any package - even DOSBox etc. pp), so that one can make sure than setup works and compiles as expected?
I also assume, that in the accompaning makefile, the above absolute path are referenced?
I am using Linux Mint 19 64-bit. (Also have 32-bit Notebook available).
BTW: compiling menuetlibc under Linux Mint 19 fails. Under 64-bit you have to instruct for 32-bit - but at the end, it fails at same location as if trying to build under 32-bit Linux.
I will report this tomorrow with error message in another thread. (But I don't know, if menuetlibc is still relevant - or is kos32-gcc environment the actual better way?)
Many thanks,
Peter
For GCC it reads:
* For a GCC program, get the toolchain at
http://ftp.kolibrios.org/users/Serge/new/Toolchain/.
Under Windows, you need the package with "msys" in name and MinGW;
after installing MinGW, unpack the package to
\MinGW\msys\1.0\home\autobuild\tools\win32, the package assumes
exactly this path. Run MinGW shell.
Under Linux, you need the package with "linux" in name
and runtime library cloog; e.g. for Debian-based distributives
use apt-get install libcloog-isl4. Unpack the package to
/home/autobuild/tools/win32, the package assumes exactly this path.
In both MinGW and Linux, make sure that the command
/home/autobuild/tools/win32/bin/kos32-gcc
invokes the compiler.
If the program uses libraries, you will also need to either compile
them separately or download SDK, if they are included to SDK.
Compiling is ultimately a sequence of calls to kos32-gcc and kos32-ld,
but filling exact parameters can be tricky, so maybe you want to
use Tup - proceed to Q2/A2 - or Make, if a maintainer has provided
Makefile.
---
I have untared as described to /home/autobuild/tools/win32.
Where exactly to I unpack the SDK available also at same link/location mentioned in the build.txt? This important information is not mentioned in the text.
Where can one download a test package (any package - even DOSBox etc. pp), so that one can make sure than setup works and compiles as expected?
I also assume, that in the accompaning makefile, the above absolute path are referenced?
I am using Linux Mint 19 64-bit. (Also have 32-bit Notebook available).
BTW: compiling menuetlibc under Linux Mint 19 fails. Under 64-bit you have to instruct for 32-bit - but at the end, it fails at same location as if trying to build under 32-bit Linux.
I will report this tomorrow with error message in another thread. (But I don't know, if menuetlibc is still relevant - or is kos32-gcc environment the actual better way?)
Many thanks,
Peter
