| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
* I need to keep deep_userdata_example hackishly built-in inside the unit tests executable, because using the external module cause a crash in Lua51 tests (module is unloaded before some deep objects are GCed...)
* copy the test script in the proper location and invoke it as part of the tests
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Everything assumes there is a _LuaVersions folder containing all supported Lua versions (binaries, libs and headers) alongside the Lanes.sln location
* After that the solutions to build the Lua binaries themselves will appear too for reference (mainly because their output folders will be configured accordingly)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* renamed makefiles:
- Shared.mk → Shared.makefile
- src/Makefile → src/Lanes.makefile
- unit_tests/Makefile → unit_tests/UnitTests.makefile
- deep_userdata_example/Makefile → deep_userdata_example/DUE.makefile
* Add a makefile for deep_userdata_example
* added a target 'unit_tests' to build them (not running them yet)
* plus some minor internal improvements
|
| |
|
|
|
|
|
|
| |
* configured to build Lanes, the example module deep_userdata_example, and the unit tests
* relies on Lua 5.1 → 5.4, LuaJIT and MoonJIT to be built and located in a fixed directory
* manual_register legacy test now uses deep_userdata_example module instead of lfs
|
|
|