TEA(ish)

Check-in [5ea9e3c525]
Login

Check-in [5ea9e3c525]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Rename teaish.tcl to teaish-core.tcl as a prelude to renaming extension.XYZ to teaish.XYZ.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 5ea9e3c5250d916127d5d95926d75da6c3a79974adf64e54a26132f10680a11a
User & Date: stephan 2025-04-09 05:45:21.529
Context
2025-04-09
06:07
Rename extension.* to teaish.*. check-in: c7ebaa23e3 user: stephan tags: trunk
05:45
Rename teaish.tcl to teaish-core.tcl as a prelude to renaming extension.XYZ to teaish.XYZ. check-in: 5ea9e3c525 user: stephan tags: trunk
05:44
Fix dir-exists check in 'make install' rules. check-in: 6d8ac64cf5 user: stephan tags: trunk
Changes
Unified Diff Ignore Whitespace Patch
Changes to doc/extensions.md.
︙︙
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235

  then bootstrapping of teaish will fail with an error to the effect
  that the offending flag has already been defined.
- **`extension-configure`**\  
  This gets called after the configuration process is bootstrapped and
  is where the extension may perform arbitrary work to configure the
  build, e.g. by processing `--flags`, performing feature detection,
  etc. It has access to the full Autosetup API, plus the APIs defined
  by [teaish.tcl][], [proj.tcl][], and any Autosetup modules it loads
  with the `use` command. After `extension-configure` completes,
  teaish will wrap up the configure process and write out any pending
  generated files. If `extension-configure` generates an error,
  configuration will (unsurprisingly) fail.


<a id="make"></a>








|








221
222
223
224
225
226
227
228
229
230
231
232
233
234
235

  then bootstrapping of teaish will fail with an error to the effect
  that the offending flag has already been defined.
- **`extension-configure`**\  
  This gets called after the configuration process is bootstrapped and
  is where the extension may perform arbitrary work to configure the
  build, e.g. by processing `--flags`, performing feature detection,
  etc. It has access to the full Autosetup API, plus the APIs defined
  by [teaish-core.tcl][], [proj.tcl][], and any Autosetup modules it loads
  with the `use` command. After `extension-configure` completes,
  teaish will wrap up the configure process and write out any pending
  generated files. If `extension-configure` generates an error,
  configuration will (unsurprisingly) fail.


<a id="make"></a>
︙︙
494
495
496
497
498
499
500
501
502
503

$ /path/to/teaish/configure ...
$ make
```

[Autosetup]: https://msteveb.github.io/autosetup/
[tcl-load]: https://www.tcl-lang.org/man/tcl8.6/TclCmd/load.htm
[proj.tcl]: /file/teaish/autosetup/proj.tcl
[teaish.tcl]: /file/teaish/autosetup/teaish.tcl
[teaish-tester.tcl]: /file/teaish/autosetup/teaish-tester.tcl
[Haiku]: https://www.haiku-os.org/








|



494
495
496
497
498
499
500
501
502
503

$ /path/to/teaish/configure ...
$ make
```

[Autosetup]: https://msteveb.github.io/autosetup/
[tcl-load]: https://www.tcl-lang.org/man/tcl8.6/TclCmd/load.htm
[proj.tcl]: /file/teaish/autosetup/proj.tcl
[teaish-core.tcl]: /file/teaish/autosetup/teaish-core.tcl
[teaish-tester.tcl]: /file/teaish/autosetup/teaish-tester.tcl
[Haiku]: https://www.haiku-os.org/
Changes to teaish/auto.def. 
1
2
3
4
5
6
7

#/do/not/tclsh
# ^^^ help out editors which guess this file's content type.
#
# Main configure script entry point for the "TEA-via-autosetup"
# framework.
use teaish
teaish-configure






|


1
2
3
4
5
6
7

#/do/not/tclsh
# ^^^ help out editors which guess this file's content type.
#
# Main configure script entry point for the "TEA-via-autosetup"
# framework.
use teaish-core
teaish-configure
Name change from teaish/autosetup/teaish.tcl to teaish/autosetup/teaish-core.tcl.
︙︙