8 Commits

Author SHA1 Message Date
sthen
25f0e460f2 Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.

This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -

- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.

- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.

devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
2018-10-24 14:27:57 +00:00
sthen
5e964ab0df bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports. 2017-07-26 22:45:14 +00:00
espie
8ac47fd9c6 use COMPILER_LIBCXX where applicable 2017-07-16 19:18:47 +00:00
sthen
bcbf44ab87 use LIBCXX 2017-04-10 11:46:18 +00:00
landry
9555a4eb84 update to spatialindex 1.8.5, tested in a bulk by ajacoutot@ 2015-09-20 07:58:20 +00:00
landry
fafc55ca49 update to spatialindex 1.8.1 2014-08-24 09:03:04 +00:00
ajacoutot
fbfca78cd6 USE_LIBTOOL=Yes is the default now. 2013-03-21 09:01:56 +00:00
landry
250d1ad069 Import spatialindex 1.8.0, needed by upcoming QGis 1.8.0.
The purpose of this library is to provide:
* An extensible framework that will support robust spatial indexing
  methods.
* Support for sophisticated spatial queries. Range, point location,
  nearest neighbor and k-nearest neighbor as well as parametric queries
  (defined by spatial constraints) should be easy to deploy and run.
* Easy to use interfaces for inserting, deleting and updating
  information.
* Wide variety of customization capabilities. Basic index and storage
  characteristics like the page size, node capacity, minimum fan-out,
  splitting algorithm, etc. should be easy to customize.
* Index persistence. Internal memory and external memory structures
  should be supported. Clustered and non-clustered indices should be
  easy to be persisted.

ok ajacoutot@
2013-03-20 21:47:34 +00:00