How do I exactly build THIS version of Dopamine? (Version 3)

[digimezzo]

How do I exactly build THIS version of Dopamine? (Version 3)

[digimezzo]

I don't yet know why the rebuild sqlite command it failing. I'll look into it. As for the collection remaining empty, and some screens not working: that is normal 🙂. Dopamine 3 is in early development and does nothing yet. Well, the settings screens are operational, and audio files are indeed and album art is downloaded from the internet. But the player does not display the collection yet, and cannot play music. That is will gradually be added in the next few weeks.

[digimezzo]

@TragicLifeHu I'll update the build instructions this week. I've reopened the issue to keep track of it.

[digimezzo]

@Cyberdroid1 Please try without running npm audit fix --force
This command is dangerous, because it updates dependencies of dependencies. This usually causes a massive amount of problems.

[digimezzo]

Please do'nt try to fix these and read this pinned issue: #68
The pinned issue contains an article that might clear things up: https://www.voitanos.io/blog/don-t-be-alarmed-by-vulnerabilities-after-running-npm-install/

[digimezzo]

It seems that the rebuild-sqlite command also rebuilt sharp. This broke the sharp module. I don't know why it breaks it though. Using native modules in Electron is quite complicated. However, it was never my intent to rebuild sharp with the rebuild-sqlite command, so I've now updated that command in package.json, so that it only builds better-sqlite3. You should be able to fix your sharp issue by doing this:

• Get the latest commit in this repository
• Delete the Sharp directory from node_modules
• Run npm install to reinstall sharp
• Run npm start again to start the application

Next time you run npm run rebuild-sqlite should not break sharp again. I'll try to further understand why rebuilding sharp breaks it though.

[TragicLifeHu]

It's not possible to build version 3 following the instruction above on Windows now. (And on my openSUSE Leap 15.2 I didn't success, too)

Microsoft had shut down everything about Visual Studio 2015, including Microsoft Build Tools 2015. Installing windows-build-tools vs2015 will result in vs2017 to be installed.
More info here: felixrieseberg/windows-build-tools#249

As for @Cyberdroid1 's issue mentioned above, I found this: https://www.programmersought.com/article/19371828050/

I don't know many about Node.js, so I just try building for fun. Sorry for troubling

[OnlyCS]

First Install NodeJS and NPM.

Linux Debian/Debian-Based:

1. Run:

curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -
sudo apt install -y nodejs

Windows:

1. Get the .exe from NodeJS Downoads
2. Open CMD Prompt and Run:

npm install --global --production windows-build-tools --vs2015

Mac:

1. Get the PKG installer from NodeJS Downloads

Or use Homebrew For Mac:

1. Install XCode from App Store

2. Open Terminal and Run:

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew update
brew install node

Building

1. If you are on Linux, Clone Dopamine with Git Clone (See readme) or with windows and mac, download and extract the zip.
   Then go into the Dopamine folder and open a Terminal/CMD Prompt window there.
   Now run:

npm install
npm run rebuild-sqlite
npm start                       # Start the program 
npm run electron:windows        # Build for Windows
npm run electron:linux          # Build for Linux
npm run electron:mac            # Build for Mac

Building for Linux gives a .AppImage, .snap, .deb, and a .rpm.
.AppImage, .snap, and .deb gives a blank screen tho. Didn't Try RPM.

[Socketlike]

Thanks! I'll definitely try this when I get back home.

…

On Sun, Sep 13, 2020, 10:48 PM dragonBall561 ***@***.***> wrote: For me, Building from Linux Gets me a .AppImage, a .deb, and a .snap. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIVWPT5PVCXXMQB6WHPAIWTSFTSUHANCNFSM4K772K6A> .

[prakharb5]

Trying to run the command npm run rebuild-sqlite fails on my Win10 PC.

Please help me. I followed everything else perfectly.

[prakharb5]

Trying to run npm start gives more error.

Is it because I ran npm audit fix --force ?

[prakharb5]

But, the command npm run rebuild-sqlite always fails. What about that?

[digimezzo]

Have you installed the Windows build tools?

[prakharb5]

Yes. See the image above I have attached.

[prakharb5]

I started again from scratch.

Running npm install keeps giving vulnerability errors.

[prakharb5]

After running npm audit fix , I still get some vulnerability errors. How do I fix that?

[prakharb5]

Ok, so I tried again, without fixing anything. It gets rebuild. And it opens on npm start. When the window opens, it is all blank. Nothing in it. The Inspect menu on the right says something that sharp module is causing problem/not found. How do I fix that?

[digimezzo]

Which version of sharp is listed when you perform this command?

npm list sharp

[prakharb5]

0.25.4

[prakharb5]

Why does the command npm run rebuild-sqlite looks for a specific file location? It should run in its present repository, right? I keep getting error for invalid file location. Though I can change the command for the same, but still, can this not be fixed?

[prakharb5]

Thanks, the app builds correctly now. The other problem that I face is this --

The library stays blank. The Manage collections button does not do anything. Please help me with this.

[digimezzo]

@TragicLifeHu With some delay, I've updated the build instructions. I tested the instructions on 2 clean Windows 10 PC's. The trick is to install Node.js including the Tools for Native Modules.