If I remember correctly someone said that maybe build directions would be added at some point. I only have have a little experience with JS but if I could build gSender it might encourage me to learn more as I’d have a use for it.
I have experience with Make, CMake, Meson, Autotools, shell scripts and probably some other build systems but I don’t even know where to begin when I look at gSender’s repository. I’m also thinking the fact that you are having trouble building it doesn’t bode well for me.
1 Like
I just have a billion problems with dependencies when I try to build. I wish there was an easier way, but for as infrequently as I’ve done it, there is always something different from the last time. My notes from the last time I successfully built gsender look like the scribblings of a madman. Despite following those scribblings, I have never been successful again.
That said, I don’t really know what I’m doing when it comes to building gSender.
This is me 
I always wonder what people will think if they look at my notebooks when I’m gone.
That reminds me my cousin just told me he’s been using Obsidian for notes, it looks interesting to me, maybe to you too if you don’t know about it.
On building gSender the closest thing I found to build directions, looked again last night, was .github/workflows/CI.yml which I’m guessing is a Travis CI configuration file in YAML. It was late and I haven’t researched Travis CI yet, if that is indeed what it’s for. Maybe the there are other continuous integration programs out there? Travis CI is the only one I’ve heard of but I’ve never looked into it because I didn’t see a need for it in small mostly solo projects.
From that file I can see it’s build with yarn. So that’s where I’m at, need to learn a little about Travis and Yarn and maybe then I could attempt to build it.
Travis CI might help, but I’m the past I’ve just built straight from visual studio on Windows. I just clone the repo, open in VS, and used npm or yarn to build. The problem comes from all the dependencies and the respective versions. I don’t know if I’m ahead or behind and when I try to update everything I get new issues. I’ve given up. I think Travis might provide a clean machine to build from, but I’d anticipate the same issues.
1 Like
Found out it’s a GitHub Actions/Workflows file. I forked the repo and I’m going to try and modify the file to use my token and see if GitHub can do a Windows build for me. I want to read up on GitHub Workflows and Actions first. They were disabled after forking and I lied to GitHub and said I knew I what I was doing. So now they’re on but I’m not sure if you even have access to the files it builds or if you need a local runner for that.
There is always too much to learn and so little time. I need some clones!
1 Like
I was reading about GitHub Actions just a few days ago. I read the “Quickstart” and realized that I didn’t have a clue what I was reading. It would not be a quck start for me.
The thing I liked about just building or running locally was that I could change the code and in less than a minute I was testing in my local instance. I didn’t have to build a windows exe to test that.
I’ll keep messing with it a bit at a time.
1 Like