Here is what I found out.
0. The package runs just fine on x86_64 (because the binaries are statically linked)
1. The installer should be put into the noextract= array, to prevent wasting time and disk space (the installer is a self-extracting ZIP file, which bsdtar will detect and extract). Unless whoever takes up maintaining this package wants to copy files without the installer's help.
2. This could be useful: http://www.openwatcom.org/index.php/Unattended_Installation
When using this method of installation, the installer should be run with -dOWDir=/opt/watcom -dDstDir=$pkgdir/opt/watcom -f=options.inf, where options.inf is a file preferably generated from inside PKGBUILD, rather than separately included (to avoid checksums getting in the way of custom builds)
Search Criteria
Package Details: open_watcom 1.9.0-3
Package Actions
| Package Base: | open_watcom |
|---|---|
| Description: | The Open Watcom C/C++ compiler, binary distribution |
| Upstream URL: | http://www.openwatcom.org |
| Category: | devel |
| Licenses: | |
| Submitter: | mathieu.clabaut |
| Maintainer: | None |
| Last Packager: | None |
| Votes: | 6 |
| First Submitted: | 2009-06-02 15:15 |
| Last Updated: | 2013-03-10 13:08 |
Dependencies (0)
Required by (2)
Sources
Latest Comments
Comment by test0
Comment by test0
Please add options=(!strip) - the executables contain error messages embedded in debug records.
Comment by WFCody
Interesting to know. I will try once more to see if I can make it compile from source instead.
Comment by unknown
This is not true. The build.sh script can be used to bootstrap a watcom compiler using gnu c/c++.
This bootstrapped compiler can then be used to compile open watcom.
Also, you could make a package `open_watcom_bin', which is a build dep for open_watcom.
Then package open_watcom provides open_watcom_bin.