Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows build of source - pro file missing #257

Open
ergodaveh opened this issue Aug 13, 2021 · 4 comments
Open

Windows build of source - pro file missing #257

ergodaveh opened this issue Aug 13, 2021 · 4 comments

Comments

@ergodaveh
Copy link

The documentation mentioned the likelihood of modifying the paths in the OpenKJ.pro file. Unfortunately, the github source does not have a the OpenKJ.pro file.

@ILightburn
Copy link
Member

ILightburn commented Aug 14, 2021 via email

@ergodaveh
Copy link
Author

Noticed the CMake pattern earlier. Had tried that build first, it wasn't successful for Windows. Then, started back with the documentation which mentioned the likelihood of pro file mods.

As such, the Cmake does build the code using build-OpenKJ-Desktop_Qt_5_12_11_MSVC2017_32bit-Debug. However, the run executable fails/crashes while launching with error "application was unable to start correctly 0xc000007b" and the start debugging exits with a warning "Debugger encountered an exception: Exception at 0x771e63b1, code: 0xc0000139: DLL entry point not found, flags=0x1 (execution cannot be continued) (first chance)"

"

@ILightburn
Copy link
Member

Probably missing the required dll files in the build directory. Try passing -DDEPLOY_DEPS=true to cmake, that should copy all the required dll files into the build directory. You can see what it does if you take a look in CmakeLists.txt down toward the bottom in the Windows specific section.

@ergodaveh
Copy link
Author

Thanks for the suggestion. I've added set(DEPLOY_DEPS TRUE) to the CmakeList >line 25
Using VS2019 the code builds and All the dlls are copied over. So that worked.

However, running debug still didn't succeed, even after selecting the Safe Setting option from Openkj

What I found was an exception in the stack with mainwindow.h > line 150.

Changed QShortcut m_scutDeleteSinger{nullptr}; to QShortcut m_scutDeleteSinger{this}; and QShortcut m_scutDeleteSong{nullptr}; to QShortcut m_scutDeleteSong{this}; and QShortcut m_scutDeletePlSong{nullptr}; to QShortcut m_scutDeletePlSong{this};

Don't know All the implications of the change on the features, but the application launches..
Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants