I think another issue is that, while this wiki article is undoubtedly
extremely useful, it relates to a rather specific task - building in a
somewhat specific set of circumstances. Without similar instructions for
other, more common, build scenarios, the article runs the risk of making
users
On 27 March 2017 at 09:38, Gordon McLeod wrote:
> Sorry, I didn't understand. The instructions seemed very useful and a normal
> part of any application documentation.
The specific issue here isn't with the instructions themselves, but
with the wiki format. All official
j10...@googlemail.com>; qgis-developer
<qgis-developer@lists.osgeo.org>
Subject: Re: [Qgis-developer] Wiki page/area for 'Building QGIS from scratch'
On 27 March 2017 at 08:10, <gor...@shieldaig.com> wrote:
> Hi Mark,
>
> I've opened a few issues on the Wiki. Some I've sorted but ot
On 27 March 2017 at 08:10, wrote:
> Hi Mark,
>
> I've opened a few issues on the Wiki. Some I've sorted but others are not
> so straight forward - but there might be a simple way I am unaware of. The
> main issues are that not all of the instructions, when used on Ubuntu
Hi Mark,
I've opened a few issues on the Wiki. Some I've sorted but others are
not so straight forward - but there might be a simple way I am unaware
of. The main issues are that not all of the instructions, when used on
Ubuntu 17.04 and I would think Ubuntu xx.x, result in `make install`
>
> Python support will be disabled.
>
I assume that these errors came from QGIS3-Dialog: correct?
That would mean that QGIS3 has found all of the libQt5* it needs
- and thus all paths are correct
The used python3 calls
- /usr/local/lib/python3.5/dist-packages/PyQt5/QtCore.so
so the pythonpath
On my Ubuntu 17.04 system in `/usr/lib/x86_64-linux-gnu/`:
`libQt5Core.so.5.7.1` exists
`libQt5Core.so.5.7` is a symbolic link
`libQt5Core.so.5` is a symbolic link
`libQt5Core.so` is a symbolic link
what do you recommend?
On 2017-03-22 04:44, Mark Johnson wrote:
On Ubuntu 17.04, which is
>
> > Can you live with a wiki version ?
>
> > - if not I will stop it
>
>
>> Hi Mark,
>
>
>> if you insist ( and I see you do :-) ):
>
> Well, nobody said it should be stopped
>
>> Then PLEASE create a system in which you make it clear
>
> WHICH version of QGIS you are trying to build on
>
>
On 22-03-17 09:41, Tim Sutton wrote:
> Richard has been researching ways to use Markdown for the docs in sphinx
> so that content can be edited directly in GitHub but that is not
> something usable ye, and I am not sure if he is still actively working
> on it.
For QGIS-3 docs I want to move to
>
> On Ubuntu 17.04, which is based on Qt5.7.1, output from
>
> `./output/bin/qgis`
>
>
>> `Couldn't load PyQt.
>
> Python support will be disabled. (a really big deal)
>
>
>> Traceback (most recent call last):
>
>File "", line 1, in
>
> ImportError: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5:
Hi
@John - sorry for the name mix up in my last post :-(
> On 22 Mar 2017, at 10:25 AM, Matthias Kuhn wrote:
>
> Normally, the way is that every project maintains the build steps for
> their own software and provides a list of dependencies. That's what we
> try to do
Hi John,
Documentation really is the way to go when it comes down to the build
software. Work in this area is very much appreciated!
The basic requirement for documentation is, that it's kept up-to-date,
maintained and concise.
Documenting the build process needs to take care of
* an update on
On 2017-03-21 20:12, Nyall Dawson wrote:
On 22 March 2017 at 08:26, wrote:
Also, I question further development using WebKit when Qt has moved to
WebEngine. Wouldn't adopting WebEngine make sense or at least present
why
it isn't.
As Tom has said, WebEngine isn't a
On 22 March 2017 at 08:26, wrote:
> Also, I question further development using WebKit when Qt has moved to
> WebEngine. Wouldn't adopting WebEngine make sense or at least present why
> it isn't.
As Tom has said, WebEngine isn't a suitable replacement. It's a very,
*very*
There's been quite a lot of discussion on the WebKit/WebEngine issue already
on the list. Bottom line - from memory WebEngine does not yet compare to
WebKit in functionality. I stand to be corrected.
Tom
-
Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon
--
View this message
It sounds great, does it work? I can suggest a reason for building from
scratch - one can compile to take advantage of multiple cores rather
than assume everyone likes slow.
I looked at these notes and the first thing I noticed was PyQt5 Version
5.8.1. Qt5.8.1 requires a change in Unicode
Replies to multiple messages inline, elow.
Tim Sutton wrote on Tue, 21 Mar 2017 at 21:43:07 +0200:
> John have you considered just running QGIS in docker - its probably
> a much easier approach than the method you have embarked upon...
I think your question was directed to
Hi
> On 21 Mar 2017, at 9:50 PM, Mark Johnson wrote:
>
> Good - I think it will get outdated quickly and history shows that such
> content does not get well maintained. If we had to do anything along these
> lines, it could be to have a small chapter which lists all
>
> Good - I think it will get outdated quickly and history shows that such
> content does not get well maintained. If we had to do anything along these
> lines, it could be to have a small chapter which lists all the QGIS
> dependencies along with a pointer to the upstream build instructions for
On 18 March 2017 at 15:43, Mark Johnson wrote:
>
>>> You should instead make your contributions to the "developers guide" -
> source is at
> https://github.com/qgis/QGIS-Documentation/tree/release_2.18/source/docs/developers_guide.
>
> I assume you mean the wiki area,
>> You should instead make your contributions to the "developers guide" -
source is at https://github.com/qgis/QGIS-Documentation/tree/release_2.
18/source/docs/developers_guide.
I assume you mean the wiki area, which is nice since I have experience in
that type of wiki
-->
On 18 March 2017 at 01:21, Mark Johnson wrote:
> For this reason I think it would be a good idea to add an area in the QGIS
> wiki with tip how this should be done,
> Something in the form of (based on the present wiki):
>
> Organize an event
> ...
> Collaborative
On 03/17/2017 05:58 PM, Mark Johnson wrote:
>>> Can you clarify on which systems you are working and which dependencies
> cause headaches?
> In my case I am working on an old machine, where many things have been
> installed in the past and cause conflicts. So until a new machine can be
> bought I
Thanks for the input, Matthias.
It's been some time since I built it from scratch, so I wouldn't be able to
provide specifics. But it was on Ubuntu 16, and Mark's comments about Qt5,
QScintylla and libpng did ring a bell for me, since the email.
I'll try again on the next couple of days and if
>> Can you clarify on which systems you are working and which dependencies
cause headaches?
In my case I am working on an old machine, where many things have been
installed in the past and cause conflicts. So until a new machine can be
bought I am attempting to get this done in a custom
Hi André and Mark,
Can you clarify on which systems you are working and which dependencies
cause headaches?
In many situations, a build of Qt is not required and doing this
requires deep understanding of all the involved libraries. I would
strongly advice anyone to first explore other
Hi all, my name is André, this is my first email on this list.
I've also struggled with building QGIS before, and besides the problems
mentioned by Mark, the default installed libraries are often incompatible
with QGIS or some of its dependencies.
I'd be willing to help with documenting my steps
Hi Mark,
Are the dependencies not available for your distribution?
Except for some very special systems (Android, very old ubuntu versions
on travis...) I never ever build these dependencies manually and just
install them.
Matthias
On 03/17/2017 04:21 PM, Mark Johnson wrote:
> For the last 10
For the last 10 days I have been attempting to build QGIS 3.0 master from
scratch.
For this QT 5 also had to be build, which is not an easy task.
In the past I had used the 'run' scripts, which installed the source
- qt-opensource-linux-x64-5.7.1.run
but after the first installment I noticed that
29 matches
Mail list logo