samba.git/lib/talloc/wscript, branch talloc-2.2.0

talloc: Release talloc 2.2.0

2019-03-21T04:06:16+00:00

 * Remove pytalloc_CObject_FromTallocPtr()
 * Remove --extra-python (a build time mode to produce Python2 and Python3
   bindings at the same time)
 * New minor version to allow Samba 4.10 to release a talloc if
   required from that branch

Signed-off-by: Andrew Bartlett 
Reviewed-by: Douglas Bagnall

build: Standardise on calling conf.SAMBA_CHECK_PYTHON() in libraries

2019-03-21T04:06:16+00:00

We do this by removing the confusing mandatory option to
conf.SAMBA_CHECK_PYTHON{,_HEADERS}(), instead just use the value of
--disable-python internally

This follows the default minimum of Python 3.4 and keeps things consistent
with the main Samba build where --disable-python is required to skip building
python bindings.

Signed-off-by: Andrew Bartlett 
Reviewed-by: Douglas Bagnall

build: Remove manual specification of minimum python version

2019-03-21T04:06:16+00:00

We now used the default of 3.4 from conf.SAMBA_CHECK_PYTHON()

Signed-off-by: Andrew Bartlett 
Reviewed-by: Douglas Bagnall

build: Remove bld.gen_python_environments()

2019-03-21T04:06:14+00:00

This was part of --extra-python support.

Signed-off-by: Andrew Bartlett 
Reviewed-by: Garming Sam

build: Remove --extra-python

2019-03-21T04:06:14+00:00

This option is quite invasive in waf and was mainly for the python3 transition.

Testing with multiple python versions can be done by testing a full compile against
multiple versions, likewise multiple different binding versions can be created
the same way.

Signed-off-by: Andrew Bartlett 
Reviewed-by: Douglas Bagnall

talloc: version 2.1.16

2019-02-26T09:39:24+00:00

* Fix standalone build of talloc.

Signed-off-by: Stefan Metzmacher

talloc: version 2.1.15

2019-01-15T10:28:13+00:00

* Deprecate talloc_set_memlimit() and talloc_autofree_context()
* Fix undefined behavior in talloc_memdup
* The build uses python3 by default:
* --extra-python would take python2 now
* To build with python2 only use:
  PYTHON=python2 ./configure
  PYTHON=python2 make
  PYTHON=python2 make install

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Karolin Seeger

PY3: detect talloc_utils (for version of python running the build)

2018-09-16T04:16:20+00:00

It seems all combinations have potential to fail here :/ however for
the moment making the assumption
  *  if python2 driving the build you are building against libpython2 (with the option of having python3 as 'extra-python'
  *  if python3 driving the build you are building against libpython3 (with the option of having python3 as 'extra-python' NOTE: this isn't inforced it probably should be !!!! In a system with python2 and python3 installed it seems waf needs PYTHON env variable to decide which libpython to build against. It's also an option that configure should use that too (to figure out which talloc_util to use or build)

However.... right now I just want the thing to build

Signed-off-by: Noel Power 
Reviewed-by: Andrew Bartlett

lib/talloc/wscript: update to handle waf 2.0.4

2018-09-05T04:37:23+00:00

Signed-off-by: Alexander Bokovoy 
Reviewed-by: Andrew Bartlett

talloc: version 2.1.14

2018-07-12T02:32:09+00:00

* Fix some typos in the comments
* Remove extra 0x prefix for the "%p" format specifiers,
  avoiding 0x0x0 strings in the output.
* make sure we link extra-python versions of libraries

Signed-off-by: Stefan Metzmacher 
Reviewed-by: Andrew Bartlett