Re: Building electron on OpenBSD
I haven't built those projects specifically, but I've had luck building Go projects on OpenBSD. I recommend building Go from source. It's quite straightforward. On OpenBSD 5.9, you can install Go from ports, then use that to bootstrap the latest 1.7.3 version. I leave the ports version intact, and set $GOROOT to the copy I've built from source. Again, I haven't built projects you link to. But I think those projects are the place to ask, rather than OpenBSD mailing lists. They would likely be able to tell you how to get around the errors you encounter, if any. -Dave On Wed, Nov 2, 2016, at 04:46 PM, Ax0n wrote: > In talking to some folks at SpiderOak few months ago, their technical > co-founder said that the ability to get Go 1.6+ and Electron working on > OpenBSD are the major technical hurdles to getting Semaphor (which is a > privacy-friendly, security-minded collaborative platform one might compare > to Slack or HipChat) running on our favorite operating system.
Building electron on OpenBSD
In talking to some folks at SpiderOak few months ago, their technical co-founder said that the ability to get Go 1.6+ and Electron working on OpenBSD are the major technical hurdles to getting Semaphor (which is a privacy-friendly, security-minded collaborative platform one might compare to Slack or HipChat) running on our favorite operating system. https://spideroak.com/solutions/semaphor/ https://spideroak.com/solutions/semaphor/source/ I'm running current, and I see we have Go 1.7 in ports, and in binary packages for some platforms. Electron's a different story. It's built on nodejs and requires python 2.7 (both of which I've also already installed) but it looks like the build scripts don't even take *BSD into consideration and I'm at a dead end. Electron: https://github.com/electron/electron/ "Build Instructions": https://github.com/electron/electron/blob/master/docs/development/build-instructions-linux.md I am not a developer. At best, I'm an excited end-user that's got a lot of sysadmin experience. I can apply patches to programs, compile basic stuff if the Makefiles aren't totally hosed, and maybe sometimes tweak code a bit, but this stuff really isn't my strong suit at all. I can sometimes get things to work. This isn't one of them. Anyone have some pointers for me? Would ports@ be a better place for this?
