I'll give you one very good reason to use a VM. It's a development
edition and they build new and revised ones daily. Not only can you
install it with a few simple commands, but two commands update it to the
latest edition painlessly in about five minutes. You can't do that at
all on the Mac platform because it doesn't have a package management
system.
On 29/09/17 17:27, David Liontooth wrote:
The compilations problems on OS X aren't serious, and I'm sure someone
already knows how to overcome them.
Since OS X is unix, it's not really a non-native platform -- it runs
the whole GNU tool chain. A vm is certainly an option, but this
doesn't look hard.
Cheers,
Dave
On 9/28/17 6:53 PM, Patrick Dunford wrote:
OK
given the limited support for non-native platforms such as MacOS the
virtualbox option is worth considering. I have drawn hundreds of km
of maps in virtual machines, performance is essentially 99.99% of
what is available on a native application.
On 29/09/17 14:50, David Liontooth wrote:
INSTALL says this under the OS X section:
Also available is a GRASS application:
http://www.kyngchaos.com/software/grass
-- though it turns out that page is for Grass 6; for Grass 7 that
page in turn points to http://grassmac.wikidot.com. Grass 6 is no
longer supported in QGIS.
These options are distinctly less appealing to me than MacPorts --
first, you have to trust the packagers blindly; secondly, the
packages don't integrate with other packages. What they're calling
"frameworks" is dependencies; these installers invite dependency hell.
QGIS should have general instructions for compiling with organized
OS X packaging systems.
MacPorts and HomeBrew do a lot of quality checking, permit easy
upgrades and uninstallations, and ensure consistent package
relations, package hash authentication, and community bug reporting.
In fact they already package QGIS, just not the unrealeased QGIS3.
Cheers,
Dave
On 9/28/17 6:14 PM, Patrick Dunford wrote:
Ok, I'm not familirar with a separate build step, don't remember
seeing that in the install documentation, unless that is a specific
variation for your platform?
On 29/09/17 14:12, David Liontooth wrote:
Hi Patrick,
I'm using today's QGIS git master and get this in the configure
output:
-- QGIS version: 2.99.0 Master (29900)
-- Could not find GRASS 7
The INSTALL file makes it clear it must be built separately, but
suggests using other "Install development frameworks".
The installation procedure for MacOS X with MacPorts is not
documented.
Cheers,
Dave
On 9/28/17 5:55 PM, Patrick Dunford wrote:
Hi, this is only a generalised comment about building packages
and may not be specific enough for your application.
When I build packages from source they come with Grass so I don't
see how it would not be included in the same scripts for the
platform you are using.
Are there any error logs for building the plugins that will show
what is happening for example the library is not found or wrong
version?
On 29/09/17 13:12, David Liontooth wrote:
I'm interested in reading LIDAR data, which appears to require
GRASS (I'm new to this).
I'm trying to compile QGIS2.99 (master) on OS X and short of
GRASS everything is working -- the program starts up with
open QGIS
MacPorts has gdal-grass @2.2.0 (gis), which pulls in grass7. It
ends up here:
/opt/local/share/grass-7.2.2/lib
so for instance
/opt/local/share/grass-7.2.2/lib/libgrass_lidar.dylib.
How do I tell the QGIS build scripts to include grass7?
Cheers,
Dave
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
_______________________________________________
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user