However, that same error message can also occur if that share has been mounted elsewhere: this can easily happen if you've already done these steps in the past, maybe using a different folder than /Volumes/Project. Well, it might definitely be the case, and the first thing we should do is to check for both of these scenarios. Such error message might let us think that A) there is already a non-empty folder on that location, or B) we have already mounted a share there: right? Mount_smbfs: mount error: /Volumes/Projects: File exists It's worth nothing that you might also catch the following (misleading) error message: Mount_smbfs: could not find mount point /Volumes/Projects: No such file or directory

Right after that I switched to the macOS VM and used the mount_smbfs command (a shortcut for mount -t smbfs) to mount the share to the /Volumes/Projects folder in the following way: The first thing I did was to share my /Projects/ root folder using a standard Windows UNC share: I assigned read and write permissions to a protected user (let's call it User) with a strong password (for example, Pass). What I am about to describe below is a UNC/SMB share between Windows and macOS, but the same procedure can also be used (with very minor differences) to connect any kind of SMB share. Which brings us to the main topic of this article. However, today I managed to further improve such technique by finding a way to entirely avoid the GitHub clone/download/NPM part, thus saving a valuable amount of disk space on my VM: I was able to do that by using a SMB share from my Windows host PC to the macOS VM. you can make amend by reading this post or just skip such topic entirely, since it's not what we'll be talking about in this post.Īnyway, I don't own a macOS, therefore I use a Virtual Machine with macOS Mojave (aka 10.14) to deal with such kind of tasks: I just launch the VM, clone (or update) my Electron project with GitHub and use NPM or YARN to build (or update) the node_modules folder: once done, I can build it with electron-builder or some similar tools. If you know Electron, you most likely know that its native multi-platform capabilities are great: you just have to run the builder from the same OS you want to build your executable installer for in case you don't, well.

Today I had to build one of my Electron-based apps for macOS, so that it could be installed and executed on macOS.

Macos samba