If you look in the patches folder, you'll see all the 'cont.c' patches I added from your PR. If you want to use it locally, it is setup to be used that way, you need ruby and two other repos for a complete build.
There's a file local.ps1.sample', it needs to be corrected for your system, and renamed local.ps1. Other than that, four symlinks/junctions are needed with the repo for git, ruby, and the two other repos.
FYI, I kind of tore ruby-loco apart and put it back together recently, and I never updated the README (how to use locally) info.
@ioquatix
Here is ruby-loco, because it's not part of Ruby, every change to Ruby has to be added as a patch file.
Normally it's just building from trunk, so that isn't an issue. For native fiber, it might get tedious...
Patches needed for the build are placed in the patches folder, test patches get placed their own folders.
If you look at a build's artifacts page (example https://ci.appveyor.com/project/MSP-Greg/ruby-loco/builds/20448680/artifacts), you'll see the files saved. One is a self contained build, one is the build files saved from one of the build folders (-ext or ext ?), and zlogs is all the test info.
If you look in the patches folder, you'll see all the 'cont.c' patches I added from your PR. If you want to use it locally, it is setup to be used that way, you need ruby and two other repos for a complete build.
There's a file local.ps1.sample', it needs to be corrected for your system, and renamed
local.ps1. Other than that, four symlinks/junctions are needed with the repo for git, ruby, and the two other repos.FYI, I kind of tore ruby-loco apart and put it back together recently, and I never updated the README (how to use locally) info.