Apparently someone pushed my commits and corrected more things; in any
case, calibre builds and starts now. Closing this bug.
Andreas
On Thu, Aug 02, 2018 at 07:04:22PM +0200, Andreas Enge wrote:
> Apparently something needs to be done since our qtwebkit is not in the
> qt installation directory. But this was also the case before, and I do
> not see how we handled this.
I tried the following:
$
On Thu, Aug 02, 2018 at 06:49:35PM +0200, Andreas Enge wrote:
> Maybe we do need to tell pyqt explicitly to compile QtWebKit?
I did a
./pre-inst-env guix environment python-pyqt
cd /tmp/guix-build-python-pyqt-5.11.2.drv-0/PyQt5_gpl-5.11.2
python configure.py --verbose
Well, I tried the following: Build python-pyqt (instead of the now already
available python2-pyqt), and stop the build after the configure phase.
In the build directory, I have groups of 5 files for modules that are going
to be built:
cfgtest_QtHelp
cfgtest_QtHelp.cpp
cfgtest_QtHelp.mk
Sorry for a wrong information in my previous message. There are indeed
two lines:
Checking to see if the QtWebKit module should be built...
Checking to see if the QtWebKitWidgets module should be built...
printed in the configure phase; but the answer is apparently "no".
Andreas
Everything built now, including calibre; but when I try to launch it,
I get the same error message as posted by Leo:
Traceback (most recent call last):
File
"/gnu/store/k6kkggp9nwlypdhda78067zqw3jm2z44-calibre-3.28.0/bin/.calibre-real",
line 20, in
sys.exit(calibre())
File
Hello,
On Thu, Aug 02, 2018 at 06:00:54PM +0300, Efraim Flashner wrote:
> How many cores do you have? My 6 core aarch64 board has 4GB of ram and
> 8GB of swap, and regularly used 4GB of the swap during building. Do you
> have any swap?
I have two (hyperthreaded) cores on my laptop and 16GB of
On Thu, Aug 02, 2018 at 02:30:20PM +0200, Andreas Enge wrote:
> Hello Efraim,
>
> thanks for all your work on the patch - you should have added a
> "Co-authored-by" line!
>
> On Wed, Aug 01, 2018 at 07:41:31PM +0300, Efraim Flashner wrote:
> > > The new qtwebkit fails to build for me. This is
Hello Efraim,
thanks for all your work on the patch - you should have added a
"Co-authored-by" line!
On Wed, Aug 01, 2018 at 07:41:31PM +0300, Efraim Flashner wrote:
> > The new qtwebkit fails to build for me. This is the tail of the output:
For me it also fails on x86_64, but due to a lack of
On Wed, Aug 01, 2018 at 10:46:56PM +1000, Brendan Tildesley wrote:
>
> The new qtwebkit fails to build for me. This is the tail of the output:
>
>
>
> /__/DerivedSources/WebCore/InternalSettingsGenerated.cpp.o -c
>
On 08/01/18 20:17, Efraim Flashner wrote:
> On Sun, Jul 22, 2018 at 11:49:14AM +0200, Andreas Enge wrote:
>> Hello,
>>
>> I ended up disabling tests (see comments in the patch).
>> Now the package builds, but tries to install into the Qt directory; at the
>> end of the cmake phase, it prints:
>>
On Sun, Jul 22, 2018 at 11:49:14AM +0200, Andreas Enge wrote:
> Hello,
>
> I ended up disabling tests (see comments in the patch).
> Now the package builds, but tries to install into the Qt directory; at the
> end of the cmake phase, it prints:
> -- Installing in the same prefix as Qt, adopting
Hello,
I ended up disabling tests (see comments in the patch).
Now the package builds, but tries to install into the Qt directory; at the
end of the cmake phase, it prints:
-- Installing in the same prefix as Qt, adopting their path scheme.
The previous version of the package contains a phase
On Sat, Jul 21, 2018 at 10:34:48PM +0200, Andreas Enge wrote:
> Does this ring a bell?
Nix has a patch:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/qt-5/5.11/qtwebkit.patch
diff --git a/Source/WebKit2/PlatformQt.cmake b/Source/WebKit2/PlatformQt.cmake
---
On Sat, Jul 21, 2018 at 09:52:25PM +0300, Efraim Flashner wrote:
> I see, debian moved to the same source. I am worried though that that
> repo hasn't seen any action in 6 months.
And it does not compile at all with our current recipe:
The custom phases 'fix-qmlwebkit-plugins-rpath and
On Sat, Jul 21, 2018 at 08:48:22PM +0200, Andreas Enge wrote:
> On Sat, Jul 21, 2018 at 09:38:30PM +0300, Efraim Flashner wrote:
> > I see a new version of Calibre was just pushed to master, does that
> > build as expected?
>
> Yes and no; it builds, but then using it fails with
> ...
> File
>
On Sat, Jul 21, 2018 at 09:38:30PM +0300, Efraim Flashner wrote:
> I see a new version of Calibre was just pushed to master, does that
> build as expected?
Yes and no; it builds, but then using it fails with
...
File
On Sat, Jul 21, 2018 at 08:13:58PM +0200, Andreas Enge wrote:
> On Sat, Jul 21, 2018 at 07:32:03PM +0200, Andreas Enge wrote:
> > So this needs to be corrected with respect to the disappearance of
> > QtWebKitWidgets from Qt, I will have a look now.
>
> This is due to the following commit:
>
>
On Sat, Jul 21, 2018 at 08:13:58PM +0200, Andreas Enge wrote:
> Interestingly enough, there is a commit in Calibre which claims to work
> on Qt 5.11 compatibility:
>
> https://github.com/kovidgoyal/calibre/commit/68bbec179abc980ebcb3f13854d2e4fd46f4897c
> So the Calibre author apparently has
On Sat, Jul 21, 2018 at 07:32:03PM +0200, Andreas Enge wrote:
> So this needs to be corrected with respect to the disappearance of
> QtWebKitWidgets from Qt, I will have a look now.
This is due to the following commit:
commit c0e7a52996edf75a403ef6c454072271fd1c277a
Author: Efraim Flashner
20 matches
Mail list logo
