Byblos - Revision history

Alexander: wip

2024-12-11T14:32:41Z

wip

← Older revision		Revision as of 14:32, 11 December 2024
Line 12:		Line 12:

	==Byblos 1==		==Byblos 1==
	Byblos 1 is the provisional Byblos SDK, running on GNU/Linux with <tt>~~musl~~</tt> ~~libc~~, either on x86-64 or AArch64. These two platforms are the only supported hosts, and on them Byblos can target the following platforms:		Byblos 1 is the provisional Byblos SDK, running on GNU/Linux with <tt>glibc</tt>, either on x86-64 or AArch64. These two platforms are the only supported hosts, and on them Byblos can target the following platforms:
	* GNU/Linux with <tt>glibc</tt> on x86-64		* GNU/Linux with <tt>glibc</tt> on x86-64
	* GNU/Linux with <tt>glibc</tt> on AArch64		* GNU/Linux with <tt>glibc</tt> on AArch64

Alexander: restructure the article

2024-11-29T11:13:47Z

restructure the article

Show changes

Alexander: /* Language classes */ new section

2024-10-29T09:17:30Z

Language classes: new section

← Older revision		Revision as of 09:17, 29 October 2024
Line 953:		Line 953:
	** Simulates x86, ARM, 68000, 65(02/816) and any bespoke A* ISAs		** Simulates x86, ARM, 68000, 65(02/816) and any bespoke A* ISAs
	* Various helper utilities for sanitising and analysing code		* Various helper utilities for sanitising and analysing code

			===Language classes===
			The Byblos compiler suite has a rigidly-dictated list of "first-class programming languages", chosen holistically by Alexander for their combination of ubiquity, expressive power and heritage. Currently, they are as follows:
			* ANSI C
			* [[C*]]
			* FORTRAN, revision 1977 (F77)
			* Verilog, revision 2005 (V05)

	Additionally, Byblos 2 integrates support for Vala using the default system compiler toolchain and libraries. This makes for an accessible and painless path to quickly writing GUI and CLI programs alike for use by developers to help author large, complex programs.		Additionally, Byblos 2 integrates support for Vala using the default system compiler toolchain and libraries. This makes for an accessible and painless path to quickly writing GUI and CLI programs alike for use by developers to help author large, complex programs.

	[[Category:Applications of mechanicalism]][[Category:Unix developments]]		[[Category:Applications of mechanicalism]][[Category:Unix developments]]

Alexander: Use dosbox-x on macOS; work around build.sh breaking with sudo

2024-09-17T21:18:09Z

Use dosbox-x on macOS; work around build.sh breaking with sudo

Alexander: explain devkitPro installation more concisely

2024-07-04T00:40:46Z

explain devkitPro installation more concisely

← Older revision		Revision as of 00:40, 4 July 2024
Line 870:		Line 870:
	Byblos 1 depends on devkitARM, MinGW, LLVM and OpenWatcom to compile code for the various targets it supports. All but OpenWatcom can be installed in binary form using package managers.		Byblos 1 depends on devkitARM, MinGW, LLVM and OpenWatcom to compile code for the various targets it supports. All but OpenWatcom can be installed in binary form using package managers.

	Follow [//devkitpro.org/wiki/devkitPro_pacman devkitPro's wiki page] to install devkitARM on macOS or GNU/Linux with respect to your distro. Once ~~installed~~, ~~get their~~ <code>gba-~~dev~~</code> ~~meta-package~~ to obtain all necessary tools and scripts for Byblos' <code>agbhb</code> and <code>agbsp</code> platforms.		Follow [//devkitpro.org/wiki/devkitPro_pacman devkitPro's wiki page] to install devkitARM on macOS or GNU/Linux with respect to your distro. Once you have <code>{dkp-,}pacman</code>, run <code>{dkp-,}pacman -S devkit-env devkitARM devkitARM-gdb gba-tools general-tools grit</code> to obtain all necessary tools and scripts for Byblos' <code>agbhb</code> and <code>agbsp</code> platforms.

	MinGW and LLVM can be installed in the typical way with your package manager. '''Do not confuse LLVM with Xcode's clang on macOS!''' Byblos on macOS uses LLVM as installed with Homebrew. The system toolchain is '''only''' used to bootstrap OpenWatcom and compile Vala code for developers.		MinGW and LLVM can be installed in the typical way with your package manager. '''Do not confuse LLVM with Xcode's clang on macOS!''' Byblos on macOS uses LLVM as installed with Homebrew. The system toolchain is '''only''' used to bootstrap OpenWatcom and compile Vala code for developers.

Alexander: /* Byblos 2 */ new section

2024-06-27T08:18:09Z

Byblos 2: new section

@@ Line 916: / Line 916: @@
 Byblos 1 entirely avoids pre-compiling native programs, instead leaning on the externally-provided toolchains to run C code and Vala code in utilities as necessary. So, it lacks a host <code>bin/</code> folder or associated <code>lib/</code> folder, which are replaced by <code>sbin/</code> and <code>slib/</code> respectively. Hashbangs are used to achieve program invocation.
-The SDK operates on the premise that the working development directory can be anywhere. SDK-specific helper scripts have provenance in <code>$BYBLOS</code> and those helper scripts should be written to correctly guess the necessary host toolchains and their locations or error out quickly on failure to find them.
+The SDK operates on the premise that the working development directory can be anywhere. SDK-specific helper scripts have provenance in <code>$BYBLOS</code> and those helper scripts should be written to correctly guess the necessary host toolchains and their locations or error out quickly on failure to find them. <!--
-<!-- XXX: pending rewrite about Byblos 2
+XXX: pending rewrite about Byblos 2
 ===Removable media and RAM drives on DOS===
 What <code>$BYBLOS</code> resolves to and its underlying media are distinguished intelligently on Unices, where the canonical resolution of <code>/opt/byblos</code> and its contents can be mount points or symbolic links to just about anything. This is not the case on DOSes, since drive letters come into play. Fortunately, the variance that we wish to accommodate is limited to those drive letters.
@@ Line 929: / Line 929: @@
 * <code>$BYBDRV</code> = <tt>E,A,B,D,C,Z</tt>
-The SDK, along with any and all programs that use its support library, will have file I/O subroutines that stitch together the base path with the drive letters to try when resolving paths. Byblos will also provide dynamic, hands-free integration with the <code>$PATH</code> executable resolution approach and will know where to look for <code>#include</code>s, libraries and other data automatically, using support library subroutines. -->
+The SDK, along with any and all programs that use its support library, will have file I/O subroutines that stitch together the base path with the drive letters to try when resolving paths. Byblos will also provide dynamic, hands-free integration with the <code>$PATH</code> executable resolution approach and will know where to look for <code>#include</code>s, libraries and other data automatically, using support library subroutines.
 [[Category:Applications of mechanicalism]][[Category:Unix developments]]

Alexander: /* Notes / is supposed to be a subheading of / Supported targets */

2024-06-27T07:41:55Z

Notes: is supposed to be a subheading of Supported targets

← Older revision		Revision as of 07:41, 27 June 2024
Line 202:		Line 202:
	\|		\|
	\|}		\|}

			=====Notes=====
			* '''<tt>bin</tt>packing''' is a highly portable method of compiling assets statically into binaries
			* For assembly, uncertainty exists about toolchain support on macOS
			* For <tt>bin</tt>packing, it may eventually work but needs further research

	====Compile time support matrix====		====Compile time support matrix====
Line 457:		Line 462:
	\| Accurate MS-DOS emulator with a focus on gaming.		\| Accurate MS-DOS emulator with a focus on gaming.
	\|}		\|}

	~~=====Notes=====~~
	* '''<tt>bin</tt>packing''' is a highly portable method of compiling assets statically into binaries
	* For assembly, uncertainty exists about toolchain support on macOS
	* For <tt>bin</tt>packing, it may eventually work but needs further research

	====Programs list====		====Programs list====

Alexander: /* Installing the SDK / rework formatting / Tool list */ djGPP not in use, replace with OpenWatcom

2024-06-25T08:54:20Z

Installing the SDK: rework formatting Tool list: djGPP not in use, replace with OpenWatcom

← Older revision		Revision as of 08:54, 25 June 2024
Line 430:		Line 430:
	\| LLVM installed on a Unix-like.		\| LLVM installed on a Unix-like.
	\|-		\|-
	\| ~~djGPP~~		\| OpenWatcom
	\| ~~Modified GCC~~ for ~~compiling~~ 16-bit DOS ~~programs~~.		\| Open source continuation of the Watcom C compiler for 16-bit DOS systems.
	\|-		\|-
	\| MinGW		\| MinGW
Line 901:		Line 901:
	With the toolchains installed, setting up the rest of the Byblos SDK is a relatively ''anodyne'' affair. In general, all utilities honour the value of <code>$BYBLOS</code> as provenance of the SDK root. If it is empty or undefined, the value defaults to <code>/opt/byblos</code>. In any case, the <code>$BYBLOS</code> root has the following hierarchy:		With the toolchains installed, setting up the rest of the Byblos SDK is a relatively ''anodyne'' affair. In general, all utilities honour the value of <code>$BYBLOS</code> as provenance of the SDK root. If it is empty or undefined, the value defaults to <code>/opt/byblos</code>. In any case, the <code>$BYBLOS</code> root has the following hierarchy:

	: <~~code~~>$BYBLOS</~~code><tt~~>/</tt> – SDK root		: <tt><u>$BYBLOS</u>/</tt> – SDK root
	:: <~~code~~>$BYBLOS</~~code><tt~~>/conf/</tt> – configuration settings		:: <tt><u>$BYBLOS</u>/conf/</tt> – configuration settings
	:: <~~code~~>$BYBLOS</~~code><tt~~>/include/</tt> – header files (<tt>.h</tt>) and assembly headers (<tt>.inc</tt>)		:: <tt><u>$BYBLOS</u>/include/</tt> – header files (<tt>.h</tt>) and assembly headers (<tt>.inc</tt>)
	:: <~~code~~>$BYBLOS</~~code><tt~~>/man/</tt> – manuals		:: <tt><u>$BYBLOS</u>/man/</tt> – manuals
	:: <~~code~~>$BYBLOS</~~code><tt~~>/sbin/</tt> – script binaries (architecture independent)		:: <tt><u>$BYBLOS</u>/sbin/</tt> – script binaries (architecture independent)
	:: <~~code~~>$BYBLOS</~~code><tt~~>/share/</tt> – shared resources and miscellanea		:: <tt><u>$BYBLOS</u>/share/</tt> – shared resources and miscellanea
	:: <~~code~~>$BYBLOS</~~code><tt~~>/slib/</tt> – script dependencies/libraries (architecture independent)		:: <tt><u>$BYBLOS</u>/slib/</tt> – script dependencies/libraries (architecture independent)
	:: <~~code~~>$BYBLOS</~~code><tt~~>/system/</tt> – private folder for internal SDK business		:: <tt><u>$BYBLOS</u>/system/</tt> – private folder for internal SDK business
	:: <~~code~~>$BYBLOS</~~code~~><tt>/target//</tt> – parent folder for target-specific sub-hierarchies (<tt></tt> is the target ident)		:: <tt><u>$BYBLOS</u>/target/<u>$t</u>/</tt> – parent folder for target-specific sub-hierarchies (<tt><u>$t</u></tt> is the target ident)
	::: <~~code~~>$BYBLOS</~~code~~><tt>/target/*/bin/</tt> – runnable binaries		::: <tt><u>$BYBLOS</u>/target/<u>$t</u>/bin/</tt> – runnable binaries
	::: <~~code~~>$BYBLOS</~~code~~><tt>/target/*/lib/</tt> – static libraries		::: <tt><u>$BYBLOS</u>/target/<u>$t</u>/lib/</tt> – static libraries
	::: <~~code~~>$BYBLOS</~~code~~><tt>/target/*/share/</tt> – target-specific miscellanea (e.g. associated production materials, emulator settings, etc.)		::: <tt><u>$BYBLOS</u>/target/<u>$t</u>/share/</tt> – target-specific miscellanea (e.g. associated production materials, emulator settings, etc.)

	Byblos 1 entirely avoids pre-compiling native programs, instead leaning on the externally-provided toolchains to run C code and Vala code in utilities as necessary. So, it lacks a host <code>bin/</code> folder or associated <code>lib/</code> folder, which are replaced by <code>sbin/</code> and <code>slib/</code> respectively. Hashbangs are used to achieve program invocation.		Byblos 1 entirely avoids pre-compiling native programs, instead leaning on the externally-provided toolchains to run C code and Vala code in utilities as necessary. So, it lacks a host <code>bin/</code> folder or associated <code>lib/</code> folder, which are replaced by <code>sbin/</code> and <code>slib/</code> respectively. Hashbangs are used to achieve program invocation.

Alexander: Rework the installation sections, making /* Getting the toolchains / and / Installing the SDK */ basically new sections outright

2024-06-25T08:48:49Z

Rework the installation sections, making Getting the toolchains: and Installing the SDK: basically new sections outright

Show changes

Alexander: swap djGPP for OpenWatcom, evenly space table columns

2024-06-23T04:45:44Z

swap djGPP for OpenWatcom, evenly space table columns

← Older revision		Revision as of 04:45, 23 June 2024
Line 202:		Line 202:
	{\| class="wikitable" width="900px" style="text-align:center"		{\| class="wikitable" width="900px" style="text-align:center"
	\|-		\|-
	! rowspan="2" \| Host		! rowspan="2" width="132px" \| Host
	! colspan="6" \| Target		! colspan="6" width="768px" \| Target
	\|-		\|-
	\| <tt>agbhb</tt>		\| width="128px" \| <tt>agbhb</tt>
	\| <tt>agbsp</tt>		\| width="128px" \| <tt>agbsp</tt>
	\| <tt>astar</tt>		\| width="128px" \| <tt>astar</tt>
	\| <tt>darwin86</tt>		\| width="128px" \| <tt>darwin86</tt>
	\| <tt>darwinm1</tt>		\| width="128px" \| <tt>darwinm1</tt>
	\| <tt>freebsd</tt>		\| width="128px" \| <tt>freebsd</tt>
	\|-		\|-
	\| <tt>linux64</tt>		\| <tt>linux64</tt>
Line 247:		Line 247:
	\|-		\|-
	\| <tt>linux64</tt>		\| <tt>linux64</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| LLVM		\| LLVM
	\| LLVM		\| LLVM
Line 255:		Line 255:
	\|-		\|-
	\| <tt>darwin86</tt>		\| <tt>darwin86</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| hb:LLVM		\| hb:LLVM
	\| hb:LLVM		\| hb:LLVM
Line 263:		Line 263:
	\|-		\|-
	\| <tt>darwinm1</tt>		\| <tt>darwinm1</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| hb:LLVM		\| hb:LLVM
	\| hb:LLVM		\| hb:LLVM
Line 281:		Line 281:
	\|-		\|-
	\| <tt>linux64</tt>		\| <tt>linux64</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| ~~djGPP~~		\| OpenWatcom
	\| MinGW		\| MinGW
	\| MinGW		\| MinGW
Line 289:		Line 289:
	\|-		\|-
	\| <tt>darwin86</tt>		\| <tt>darwin86</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| ~~djGPP~~		\| OpenWatcom
	\| MinGW		\| MinGW
	\| MinGW		\| MinGW
Line 297:		Line 297:
	\|-		\|-
	\| <tt>darwinm1</tt>		\| <tt>darwinm1</tt>
	\| ~~djGPP~~		\| OpenWatcom
	\| ~~djGPP~~		\| OpenWatcom
	\| MinGW		\| MinGW
	\| MinGW		\| MinGW
Line 308:		Line 308:
	{\| class="wikitable" width="900px" style="text-align:center"		{\| class="wikitable" width="900px" style="text-align:center"
	\|-		\|-
	! rowspan="2" \| Host		! rowspan="2" width="132px" \| Host
	! colspan="6" \| Target		! colspan="6" width="768px" \| Target
	\|-		\|-
	\| <tt>agbhb</tt>		\| width="128px" \| <tt>agbhb</tt>
	\| <tt>agbsp</tt>		\| width="128px" \| <tt>agbsp</tt>
	\| <tt>astar</tt>		\| width="128px" \| <tt>astar</tt>
	\| <tt>darwin86</tt>		\| width="128px" \| <tt>darwin86</tt>
	\| <tt>darwinm1</tt>		\| width="128px" \| <tt>darwinm1</tt>
	\| <tt>freebsd</tt>		\| width="128px" \| <tt>freebsd</tt>
	\|-		\|-
	\| <tt>linux64</tt>		\| <tt>linux64</tt>

← Older revision		Revision as of 21:18, 17 September 2024
Line 879:		Line 879:
	# Run <code>xcode-select --install</code>		# Run <code>xcode-select --install</code>
	# Follow [//brew.sh/#install brew.sh#install]		# Follow [//brew.sh/#install brew.sh#install]
	# Run <code>brew install dosbox</code>		# Run <code>brew install dosbox-x</code>
	# Manually choose the latest release from [//github.com/open-watcom/open-watcom-v2/releases the repository]		# Manually choose the latest release from [//github.com/open-watcom/open-watcom-v2/releases the repository]
	#* Select the source code <tt>.tar.gz</tt> in particular		#* Select the source code <tt>.tar.gz</tt> in particular
	# <tt>un</tt><code>tar</code> the source into a <code>$dir</code> of your choice		# <tt>un</tt><code>tar</code> the source into a <code>$dir</code> of your choice
	# Set environment variable <code>OWTOOLS=CLANG</code>		# Set environment variable <code>OWTOOLS=CLANG</code>
	# Set environment variable <code>OWDOSBOX=dosbox</code>		# Set environment variable <code>OWDOSBOX=dosbox-x</code>
	# Run <code>export OWTOOLS OWDOSBOX</code>		# Run <code>export OWTOOLS OWDOSBOX</code>
	# Run <code>cd $dir</code>		# Run <code>cd $dir</code>
	# Run <code>./build.sh</code>		# Run <code>./build.sh</code>
			# Run <code>./build.sh rel</code>
	# Run <code>sudo mkdir /opt/watcom</code>		# Run <code>sudo mkdir /opt/watcom</code>
	# Run <code>sudo ./~~build~~.sh /opt/watcom</code>		# Run <code>sudo cp -a rel/. /opt/watcom/</code>
	# Append the following lines to your <tt>.profile</tt> (or your equivalent to <tt>.profile</tt>):		# Append the following lines to your <tt>.profile</tt> (or your equivalent to <tt>.profile</tt>):
	#* <code>WATCOM=/opt/watcom</code>		#* <code>WATCOM=/opt/watcom</code>