01:03 <JacobWeisz[m]> The draw.io build process for Sandstorm is kinda weird. But it's documented!

01:10 <JacobWeisz[m]> Basically it copies everything from everywhere else in the repo into a temp folder. And they've since reorganized the whole repo and broke everything.

01:39 <JacobWeisz[m]> Ian, I have no idea why a Sandstorm server.c++ file is in the build process.

01:39 <JacobWeisz[m]> All I know is that it is where I am failing.

01:43 <JacobWeisz[m]> https://github.com/ocdtrekkie/drawio/tree/sandstorm has my current progress. The latest commit readds the readme for building Sandstorm, I updated (most) of the file locations so stage.sh works, and currently it explodes on a ton of capnproto stuff when I "make dev".

01:43 <JacobWeisz[m]> I did try installing capnproto from the git repo so I'd have the latest.

01:47 <isd> I doubt the problem is it's expecting a _new_ version of capnproto :P. let me have a look.

01:48 <JacobWeisz[m]> I also tried apt-get installing capnproto first, that didn't work either.

01:48 <JacobWeisz[m]> My luck, it wants some version in the middle of those two.

01:49 <isd> Oh wow, this doesn't use sandstorm-http-bridge.

01:50 <JacobWeisz[m]> I have no idea where server.c++ came from. Maybe someone Sandstorm team wrote it for them?

01:50 <isd> Some of this looks like copypasta from the app index.

01:51 <JacobWeisz[m]> I found at least one random line that was copied from util.h, it seemed like

01:51 <JacobWeisz[m]> I imagine copypasta is a healthy starting point.

02:43 <JacobWeisz[m]> Okay, I'll try adding that in my next attempt. I am betting there are some directories not included in the current staging script, so I'll have to review that yet.

02:44 <JacobWeisz[m]> I already had to change one or two things, like gfind which is the MacOS version of find.

04:21 <JacobWeisz[m]> Yup, pkg-config was all that was the problem.

04:22 <JacobWeisz[m]> I'll fix up the instructions, review what is and isn't being pulled in by stage.sh for mossing stuff, update all the branding to diagrams.net, and email the guy for the publishing key.

13:37 <JacobWeisz[m]> I think I'm gonna move more of the instructions into the actual scripts though. At least the setup one.

13:38 <JacobWeisz[m]> sshing into the VM just to install some packages seems like it was done without really knowing the standard vagrant-spk flow of things.

14:07 <isd> +1

14:08 <isd> (Also probably the instructions shouldn't suggest that you to re-do vagrant-spk setupvm...)

14:09 <JacobWeisz[m]> Yeah, I'd need to replace that with having the files already in the folder and having stage.sh move them to the right place.

14:11 <JacobWeisz[m]> I was gonna update the Vagrantfile and maybe use Buster (no reason not to for the diy stack) until I realized this strategy doesn't even commit the Vagrantfile anyways.

14:11 <JacobWeisz[m]> I mean, the upside to this strategy, arguably, is that the vagrant-spk VM is never out of date...

14:13 <isd> The downside being reproducibility.

14:14 <JacobWeisz[m]> I'll get everything working well with the current build strategy first, and then work on changing it around after that, I think.

14:14 <isd> +1