-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Cannot open include file: 'pthread.h' #11596
Comments
Not a Mixxx issue. |
@ikr83 has reported the same issue here: #11621 (comment) Even if we know that it works if all is "correctly" configured it seems to be hard to find out what is correct. |
Related: |
I followed instructions here ... https://github.com/mixxxdj/mixxx/wiki/Compiling%20on%20Windows ... and it works even if I didn't understand everything. |
Fine, now it is working. Can you reproduce your original issue? My idea is to make it initially work for new contributors or at least give less obscure error messages. |
The biggest difference is that I used CMake directly from VS2019 instead of using the command line method. To be more specific: At the beginning, Download Visual Studio Community
Download Rust + Install Installation sccache Download Mixxx source code I tried with this code first: Then I tried with this code: Same results at the end... Download + UNZIP code Download buildenv
Visual Studio Open a local folder "mixxx folder" Change the configuration and wait for CMake to finish each time: Press CTRL+SHIFT+B to generate everything. After that, I can load Mixxx/build from the portable folder, but I can't find the Windows installer. The portable version of Mixxx works with my default preinstalled settings folder. Originally, everything started from bug #11621. During CMake, I saw error messages appearing, but they did not halt the generation process. However, only the "portable" folder contains a mixxx.exe executable. Maybe this is normal, I'm not sure... |
The x_64_portable.cmake.sortie.txt looks good. Can you remember what was the issue? Maybe you could remember what you did and reproduce this in a fresh build directory? In your current build we have two minor issues:
|
**What didn't work for me Use Windows Command line (instead of VS2019) + don't install rust + install sccache with scoop **What worked better Download Rust + Install Installation sccache Use VS2019 to build First time I build, so I didn't expect anything ... I knew cpack is necessary to generate a package but I didn't know how to use it. I'm not ready to start contributing for the moment but I will because I want to add the option to use a custom settings folder. If during the installation of Mixxx, I can choose the folder where I place my configuration files, then I will place them in a folder connected to the cloud so that I can use Mixxx with different computers. Currently, I use robocopy and it works well, but it's still a makeshift solution. Next Episode... :) Thanks a lot, I'll read the Bugfix Workflow. |
Ok, thank you. I will have a look how to improve this.
This can already be done with a modified link on the desktop. You can add there any '--settingsPath` not sure if the database file itself works from a cloud though. A solution that makes this feature more discoverable would be a nice addition. |
Hi, I haven't given up, I retried everything and I still can't build. I reinstalled a clean environment VS2019.mp4:/ |
If a make a second "cmake .." just after the first one, there is less errors. And the error at the end "cmake --build ." become: |
Here's a CHATGPT analysis of the specific errors:
|
Cool, I consider your build correctly configured. During the first cmake run it probes various things where some are failing. The issue with "u_int8_t" looks like a typo. I have no idea why our CI did not detect it. Try to use uint8_t instead. |
Please pull my patch and check if anything else is failing:
|
I fix u_int8_t, the build completes successfully, I start mixxx.exe and it works! :D Next step, In VS2019 In NSISOutput.log I can see mixxx_install_logo.bmp in my explorer... project.nsi" on line 571 I delete the _CPack_Packages folder, and I remember you had advised me to use "cpack -G WIX," but I don't have WIX installed. CMake Error at C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.20/Modules/Internal/CPack/CPackWIX.cmake:12 (message): I run cpack -G WIX CPack Error: Error while executing CPackWIX.cmake I think there is a problem with new Wix Version "For command-line afficionados, most executables have been merged into a single wix.exe tool with commands. For example, in WiX v3, you might build by calling Candle.exe one or more times to compile your authoring and then calling Light.exe to link and bind the compiled authoring into an .msi package. In WiX v4 using wix.exe, that's one command: wix build -o product.msi product.wxs." :/ |
This is because this affects only bulkcontroller.cpp and the Windows CI builds are with BULK=OFF. |
Is that correct? I think we should as as align our home builds with the CI defaults. |
Another pitfall, sorry. Thank you for all the hints. I will take a look. |
Yes, because BULK USB can't be used for security reasons without installing additional drivers on Windows, it's not useable for normal users. |
Presets are very welcome to build different configurations on the same host. This allows a lot more than just "Debug" and Release. We can also auto generate a CMakeUserPreset.json like we currently do with "CMakeSettings.json" Apart CMake presets, we should also choose reasonable defaults when starting cmake without "--preset" |
Sorry for using the same page to address all my little issues to achieve the build+pack... but since I started, I feel obligated to continue... Regarding my "build issue", changing "u_int8_t" to "uint8_t" was enough... Tonight, I will uninstall Wix 4, install Wix 3, and see if "cpack -G WIX" works better. |
This is issue is the perfect place for such things. I expect that there are are number of users suffer like you, but instead of analyzing the issue they give up. |
Oki! cpack -G WIX with Wix4 doesn't work for me ( because there is the candle issue https://wixtoolset.org/docs/fourthree/ ). Thank you very much! |
To resume, Windows environment setup To build Optionnal To make an installer after building Run x64 Native Tools Command Prompt for VS 2019 cd c:/users/david/Desktop corrections cd ../build :D |
This means we are done, once the pending PRs are merged? I am sure the scoop installation of sccache will also work. Maybe we should describe the scoop way as recommended. @JoergAtGithub what do you think? sccache is by the way optional, it is strongly recommend for contributors that build different branches though. |
Indeed, when the source code is up to date, it will be fine! But be careful with the cpack -G WIX command, which requires the installation of WIX v3. The latest version of WIX (v4) doesn't work (candle issue). I don't think Rustup installs from source code (the same goes for Scoop). |
Bug Description
While compiling, I get this error message. How do I solve this problem?
fatal error C1083: Cannot open include file: 'pthread.h': No such file or directory
Version
2.3.5
OS
Windows 10, Visual Studio Community 2019
The text was updated successfully, but these errors were encountered: