I have build ParaView superbuild following steps that I found in another question.
Steps to build ParaView superbuild in Windows 10:
Install Visual Studio 2015 community with all C++ related tools
Install cmake
Install git bash
Install Ninja
Install Qt 5.9.9 VS2015 64 bits
then :
Open VS2015 x64 Native Tools Command Prompt and execute: cmake-gui
ENABLE_qt5 and USE_SYSTEM_qt5
ENABLE_python
ENABLE_python2
and add: Qt5_DIR = C:/Qt/5.9.9/msvc2015_64/lib/cmake/Qt5
configure
generate
Result:
Determined source version for paraview: 5.7.0
Enabling cxx11 as requested.
Enabling ftjam as requested.
Enabling nlohmannjson as requested.
Enabling zlib for: hdf5
Enabling szip for: hdf5
Enabling hdf5 for: paraview
Enabling python2 as requested.
Enabling python as requested.
Enabling qt5 as requested.
Enabling paraview as requested.
Building projects: cxx11, ftjam, nlohmannjson, zlib, szip, hdf5, python2, python, qt5, paraview
Configuring done
Generating done
Then:
close cmake-gui
ninja
After a couple hours, it seems to build successfully.
I then download Clone1 from https://gitlab.kitware.com/paraview/paraview/tree/master/Examples/CustomApplications
Open VS2015 x64 Native Tools Command Prompt and execute: cmake-gui
Add:
Qt5_DIR = C:/Qt/5.9.9/msvc2015_64/lib/cmake/Qt5
ParaView_DIR = C:\Users\user\Desktop\paraview\buildvs2015\install\lib\cmake\paraview-5.7
Then:
configure
generate
And I got:
Found Python2: C:/Users/user/Desktop/paraview/buildvs2015/install/lib/python27.lib (found suitable version "2.7.15", minimum required is "2.7") found components: Development
Found OpenGL: opengl32 found components: OpenGL
Found ZLIB: C:/Users/user/Desktop/paraview/buildvs2015/install/lib/zlib.lib (found version "1.2.11")
Looking for pthread.h
Looking for pthread.h - not found
Found Threads: TRUE
Skipping example: Clone1 example requires PARAVIEW_USE_QT to be enabled. Please rebuild ParaView (or point to a different build of ParaView) with PARAVIEW_USE_QT set to TRUE
Configuring done
I have ENABLE_qt5 and USE_SYSTEM_qt5 activated, why am I getting this? How can I fix it?
Use the Clone1 example from ParaView 5.7.0, not from master.
You can find the sources in
C:\Users\user\Desktop\paraview\buildvs2015\superbuild\paraview\src\Examples\CutstomApplications\Clone1
Related
I am building the Visual Studio Code from the source checked out from the git repository:
git clone https://github.com/microsoft/vscode
I am building using:
export NODE_OPTIONS=--max_old_space_size=2048
./scripts/npm.sh install --arch=armhf
./scripts/code.sh
I am using node 10.16.3 on a Raspberry PI 4, using Raspbian buster
There were no errors during build.
The installation downloads a precompiled version of electron on the first run.
However each time I try and run code, it starts but with an error:
[storage state.vscdb] open(): Unable to open DB due to Error: Cannot find module '../build/Release/sqlite
If I look in node_modules/vscode-sqlite3/build/Release/
I can see:
sqlite3.a
sqlite.a
It is unclear to me why electron/vscode cannot find this library. I would be greatful for any pointers on how to tell the runtime where to look for the modules.
On inspecting the build scripts and after many painful experiments, I've found and solved the 2 problems leading to this error.
The fact that .a static libraries are left behind hinted that some settings in the binding.gyp, config.gpy and/or makefiles are wrong, as Native Node Modules are normally dynamic libraries with an .node extension. One conditional line in the binding.gyp file under vscode-sqlite3 seems to the the culprit:
...
["target_arch=='arm'", {"type": "static_library"}]
...
Disable that line (by removing it or changing 'arm' to something else) and then run:
node-gyp configure
to regenerate the config.gpy file(s) under the build directory. Then build the module with:
node-gyp build
A sqlite.node will be generated in build/Release.
Unfortunately, the latest electron ABI version rarely matches that of the Node.js version. In my configuration, the electron ABI version is 72 (v6.0.12) but the latest stable Node version is for ABI 64. Therefore we have to do an electron-rebuild to update the sqlite.node to match the electron version.
To do this, you would have to first install electron-rebuild (yarn add electron-rebuild) then run electron-rebuild by giving supplying explicitly the version number of the electron binary that vscode downloaded:
electron-rebuild -v 6.0.12 -m /home/dev/vscode -o vscode-sqlite3
Of course you would have to state the version number of your particular version of electron you are building for.
(Please look up electron-rebuild --help for the meaning of the options. It takes a while to rebuild the binary module...)
The resulting sqlite.node can then be moved into the build/Release/. directory under the vscode project directory. Voila, we have a working latest version VS-Code for Raspbian!
Running:
./myapp -platform wayland
gives:
This application failed to start because it could not find or load the
Qt platform plugin "wayland" in "".
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
offscreen, vnc, xcb.
Reinstalling the application may fix this problem. Aborted (core
dumped)
Following the instructions: How to build qtwayland?
Running qmake gives:
Running configuration tests...
Done running configuration tests.
Configure summary:
Qt Wayland Client ........................ no
Qt Wayland Compositor .................... no
Note: No wayland-egl support detected. Cross-toolkit compatibility disabled.
The qtwayland README indicates 2 dependencies:
xkbcommon 0.2.0 - http://xkbcommon.org/
wayland 1.6.0 - http://wayland.freedesktop.org/
On fedora 28, libxkbcommon is installed by default. In addition I also installed libxkbcommon-devel
dnf whatprovides *wayland*
returns no results, although my gnome session is running under wayland.
I see I can download wayland from https://wayland.freedesktop.org/releases.html.
I downloaded and decompressed 1.15, but not sure what to do with decompressed source: do I build it? do I need to put it somewhere where qtwayland can find it?
I see that the following file exists by default in fedora 28:
/usr/lib64/qt5/plugins/wayland-graphics-integration-server/libwayland-egl.so
But copying it to ~/Qt/5.10.1/gcc_64/plugins/platforms
does not resolve my application startup errors.
Question: how to get my Qt application to run under wayland?
Added in response to bobbaluba questions below:
Am trying to build QtWayland against the official Qt Binaries because it is not included.
Installed wayland-devel as suggested, but qmake still reported no configure for Qt Wayland Client, as per the message above.
Tried to install qt5-qtwayland using dnf, which reported:
Package qt5-qtwayland-5.10.1-2.fc28.x86_64 is already installed, skipping.
The following might be relevant:
? sudo dnf whatprovides libwayland-egl.so
Last metadata expiration check: 0:18:44 ago on Wed 09 May 2018 09:15:20 PM +08.
qt5-qtwayland-5.10.1-2.fc28.i686 : Qt5 - Wayland platform support and QtCompositor module
Repo : fedora
Matched from:
Provide : libwayland-egl.so
? find / -name libwayland-egl.so* -print
/usr/lib64/libwayland-egl.so
/usr/lib64/qt5/plugins/wayland-graphics-integration-server/libwayland-egl.so
? sudo ldconfig -p | grep wayland-egl
libwayland-egl.so.1 (libc6,x86-64) => /lib64/libwayland-egl.so.1
libwayland-egl.so (libc6,x86-64) => /lib64/libwayland-egl.so
Installed Qt 5.11.0rc which resulted in
~/Qt/5.11.0/gcc_64/plugins/wayland-graphics-integration-server/libwayland-egl.so
~/Qt/5.11.0/gcc_64/plugins/wayland-graphics-integration-server/libwayland-egl.so.debug
being added to ~/Qt/5.11.0/gcc_64/plugins/platforms.
cmake's CMakeFile.txt suddenly stopped working when I installed Qt5.11rc - with gcc unable to find Qt headers like QDate.
Tried compiling the example project 'addressbook' using Qt5.11 and got:
QSocketNotifier: Can only be used with threads started with QThread
Using Wayland-EGL
Using the 'xdg-shell-v6' shell integration
In short, using the Qt5.11rc seems to resolve the issue.
Why does configuring QtWayland fail?
I'm assuming (correct me if I'm wrong) that you are trying to build QtWayland against official Qt binaries that do not include QtWayland.
Do you have development packages installed? In your case I think it should be wayland-devel.
Btw, the libwayland-egl.so you see, is your distro's version of the qt wayland-egl buffer integration (and not the same as the libwayland-egl.so dependency which qmake complains is missing). However, you should still be able to build QtWayland without wayland-egl, so I'm not sure what this is about.
Other options:
1. Use official QtWayland binaries
You are probably running into this problem because Qt packages did not previously include QtWayland.
However, starting with Qt 5.11.0 the official Qt binaries should include QtWayland, so the easiest thing would probably be to install Qt 5.11.0 or newer.
2. Use the distro's version of Qt (and Qt Wayland)
Install and use Qt from the distro, make sure you also install qtwayland (on Fedora I think it's qt5-qtwayland).
If I try to open an existing project in Qt Creator I always get "No valid kits found".
I found a lot of Q&A around this, but on my installation I am not able to select a valid Qt version because:
In Build&Run->Kids->Desktop->QtVersion: None
I can not see any other entry in this field.
As already mentioned: It is a Fedora 25 x86_64 version.
Qt Creator gives in comand line:
Warning: No kit 'qt.57.gcc_64_kit' found. Continuing.
Is this a file which should exist somewhere? Can it be downloaded somewhere? Manual config seems to be not possible, because qt version can not be selected.
Is there any package which I did not have installed? Is there any meta package which I can use to get a valid installation?
What I have installed:
rpm -qa | grep qt5
dbusmenu-qt5-0.9.3-0.11.20150604.fc24.x86_64
qt5-qtbase-gui-5.7.0-3.fc25.x86_64
qt5-qtwebchannel-5.7.0-2.fc25.x86_64
qt5-qttools-static-5.7.0-3.fc25.x86_64
qt5-qtconfiguration-devel-0.3.1-2.fc24.x86_64
adwaita-qt5-0.4-3.fc25.x86_64
qt5-qtsvg-devel-5.7.0-2.fc25.x86_64
qt5-qtbase-common-5.7.0-3.fc25.noarch
qt5-qtlocation-devel-5.7.0-2.fc25.x86_64
qt5-qttools-libs-designer-5.7.0-3.fc25.x86_64
qt5-qtx11extras-devel-5.7.0-2.fc25.x86_64
qt5-qtserialport-5.7.0-2.fc25.x86_64
qt5-qttools-devel-5.7.0-3.fc25.x86_64
qt5-qtconfiguration-0.3.1-2.fc24.x86_64
qt5-qtwayland-devel-5.7.0-2.fc25.x86_64
qt5-qttools-libs-clucene-5.7.0-3.fc25.x86_64
qt5-qtlocation-5.7.0-2.fc25.x86_64
quazip-qt5-0.7.2-1.fc25.x86_64
qt5-qttools-libs-designercomponents-5.7.0-3.fc25.x86_64
qt5-qttools-5.7.0-3.fc25.x86_64
qt5-qtenginio-devel-1.6.1-2.fc25.x86_64
qt5-linguist-5.7.0-3.fc25.x86_64
qt5-qtwebsockets-devel-5.7.0-1.fc25.x86_64
qt5-qtconnectivity-devel-5.7.0-2.fc25.x86_64
qt5-qtsvg-5.7.0-2.fc25.x86_64
qt5-qtquickcontrols-5.7.0-1.fc25.x86_64
qt5-qtwayland-5.7.0-2.fc25.x86_64
qt5-devel-5.7.0-9.fc25.noarch
qt5-qtxmlpatterns-5.7.0-2.fc25.x86_64
qt5-qtwebkit-5.7.0-2.fc25.x86_64
qt5-qtserialport-devel-5.7.0-2.fc25.x86_64
qt5-qtaccountsservice-devel-0.6.0-2.fc24.x86_64
qt5-qttools-libs-help-5.7.0-3.fc25.x86_64
qt5-qtmultimedia-5.7.0-2.fc25.x86_64
qt5-qtimageformats-5.7.0-2.fc25.x86_64
qt5-qtsensors-5.7.0-2.fc25.x86_64
qt5-qtdoc-5.7.0-1.fc25.noarch
qt5-designer-5.7.0-3.fc25.x86_64
qt5-qtbase-static-5.7.0-3.fc25.x86_64
qt5-qtenginio-1.6.1-2.fc25.x86_64
qt5-qt3d-5.7.0-2.fc25.x86_64
qt5-qtbase-5.7.0-3.fc25.x86_64
qt5-qtdeclarative-devel-5.7.0-2.fc25.x86_64
qt5-rpm-macros-5.7.0-9.fc25.noarch
qt5-qhelpgenerator-5.7.0-3.fc25.x86_64
qt5-qtwebsockets-5.7.0-1.fc25.x86_64
qt5-qtconnectivity-5.7.0-2.fc25.x86_64
phonon-qt5-4.9.0-3.fc25.x86_64
qt5-qtscript-5.7.0-2.fc25.x86_64
qt5-qtwebchannel-devel-5.7.0-2.fc25.x86_64
qt5-gstreamer-devel-1.2.0-11.fc25.x86_64
qt5-qtaccountsservice-0.6.0-2.fc24.x86_64
phonon-qt5-backend-gstreamer-4.9.0-1.fc25.x86_64
qt5-qtscript-devel-5.7.0-2.fc25.x86_64
qt5-qtbase-devel-5.7.0-3.fc25.x86_64
qt5-qtx11extras-5.7.0-2.fc25.x86_64
polkit-qt5-1-0.112.0-8.fc25.x86_64
qt5-qdoc-5.7.0-3.fc25.x86_64
qt5-qtdeclarative-static-5.7.0-2.fc25.x86_64
qt5-qtwebkit-devel-5.7.0-2.fc25.x86_64
qt5-gstreamer-1.2.0-11.fc25.x86_64
qt5-qtdeclarative-5.7.0-2.fc25.x86_64
qt5-qtsensors-devel-5.7.0-2.fc25.x86_64
qt5-qttools-common-5.7.0-3.fc25.noarch
qt5-qtmultimedia-devel-5.7.0-2.fc25.x86_64
qt5-qtxmlpatterns-devel-5.7.0-2.fc25.x86_64
qt5-qt3d-devel-5.7.0-2.fc25.x86_64
I also develop with Qt Creator on Fedora 25, and it works for me.
Here is how I usually do it:
dnf install make gcc-c++ gdb
dnf install qt5*-devel
dnf install qt-creator
After this, I've got a working Qt Creator configuration on a fresh Fedora 25 (that I just installed from scratch yesterday).
To be honest, I'm not sure what you might have been doing wrong, but I have a few ideas:
Did you upgrade from a previous OS version or maybe copy the configuration of a previous Qt Creator version to your new installation?
Check that you have a compiler and build environment (make, gcc, ...) installed
If its configuration is corrupt, you could try deleting ~/.config/QtProject and Qt Creator might recognize your stuff.
Try to delete the *.pro.user file of your project if it may have been generated by a previous Qt Creator version
In any case, you can fix the configuration relatively easily.
Go to Tools -> Options
Select Build & Run
On the Compilers tab you should see your installed compiler in the auto-detected section. If you have a compiler installed but it isn't recognized, add it here manually.
On the Qt Versions tab, the version I installed from the Fedora repo (currently 5.7.0) appears in the Manual section (even though I didn't add it manually). You can add it by browsing to /usr/bin/qmake-qt5.
On the Kits tab, I have a single Manual entry called Desktop, which is basically set to use the compiler and Qt version mentioned above.
I got it:
qtcreator was not able to find my qmake installation, because in the fedora packages qmake is:
-rwxr-xr-x. 2 root root 2921520 19. Jul 14:51 /usr/bin/qmake-qt5
Adding a softlink to
lrwxrwxrwx. 1 root root 18 5. Dez 17:17 /usr/bin/qmake -> /usr/bin/qmake-qt5
did NOT help!
You have to point to the correct qmake via :
Build&Run -> Kits -> Manual -> Desktop -> Qt-Version -> Manage -> "Select qmake with file-browser"
Now it seems to find a qt version.
In "Details" the dialog prints "Qt version 5.7.0 for Desktop"
Why there is not a simple output: "Can not find qmake"?
OK, seems to be a bit special to fedora which install qmake to different file name.
Based on #SteeveDroz comment that worked for me on Fedora 29:
Remove the path to the shell script and select /us/bin/qmake-qt5.
Now it doesn't complain about the wrong version.
The "No valid kits found" error can be caused by many things (e.g. missing g++ compiler). Here's a video I just uploaded that shows a clean install of Qt 5.13 on a clean install of Fedora 30 KDE:
https://www.youtube.com/watch?v=DQKoNwg5afU
The error
When I run pip install PySide – whether in a virtual environment or not – build fails with the following error:
... [lots of build info, including a few warnings but no errors, for shiboken]
Linking CXX executable shiboken
ld: framework not found QtCore
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Seeing as I have QtCore installed and the framework present (see below), I'm not sure why that should be.
Setup info
Software versions
OS X 10.8.2
Qt 4.8.4 from the developer distributed binaries
Python 3.3 installed and working normally
XCode 4.6
Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn)
Target: x86_64-apple-darwin12.2.1
Virtual environment generating using pyvenv (with and without --no-site-packages)
Other configurations attempted
Python 2.7 installed and working normally
Virtual environment generated using mkvirtualenv (with and without --no-site-packages)
virtualenv 1.8.4
mkvirtualenv 3.6
System configuration
I've confirmed that QtCore is in fact installed correctly: ls /Library/Frameworks shows a number of Frameworks, including QtCore.Framework.
My path currently includes both /Library/Frameworks/QtCore.framework and /Library/Frameworks/QtCore.Framework/Versions/4 – the former of which has a symbolic link to the component in the latter location. I've even tried it with /Library/Frameworks, though for obvious reasons I didn't expect that to help and it did not.
Other notes
I've tried the same thing with easy_install and by doing a pull from the Git repository and building manually using setup.py. As one would expect, they all return the same results.
Things I've already read
PyPi Installation walkthrough
Link error: QtCore.framework/Versions/4/QtCore for architecture x86_64 (Stack Overflow) – but it seems the linker is already asking for the framework, based on the error message I'm receiving.
Mac OS X: trying to link (ld) against a framework (Stack Overflow) – general info on linking against Frameworks; again, I seem to have this covered.
OSX deployment target confusion for 2.8.10 (CMake Mailing list) – looks like a very similar error, but I don't have direct control of the -isysroot flag using pip (or easy_install or even python setup.py) for one and for another, installation structure seems to have changed substantially between OS X 10.6 and 10.8. For example, /Developer no longer has the SDKs directory in it at all.
CMake bug report 0013765 – this one looks exactly the same, but appears to have been patched, so I'm not sure why it would still be causing me a problem.
Preferences
I'm not using a package manager like Homebrew or MacPorts at this time, and I'd prefer not to, either, as I need to get as close as possible to a platform-agnostic installation procedure for this (we're looking at doing cross-platform development; I'll ultimately be targeting Windows applications primarily, but need to see if it's workable on my Mac development machine outside a VM).
It needs to be able to work with a Python 3-style virtual environment (pyvenv) setup, as that's our preferred means of isolating our particular requirements.
I created an application using Imagemagick library with Qt on Mac.
Now that I want to deploy the application for windows:
I installed the imagemagick library
on my pc,
I installed the SDK version of QT 4.7
I added my include and lib paths
And when I go run the application I'm getting errors that I think they are related to mingw32.
here are the build issues:
and here is the compile output:
Can someone Identify the error ?
What do I have to do to deploy the application for windows?
I also tried to use a Mingw32 version of my library but again, It didnt work:
When I put -lmagick after the lib it says file lmagick cannot ne found
and when I try to build unticking the shadow build checkbox in the build settings, it give me the errors in the first screenshoot. Thank you
See the answer to this question.