[no subject]

[Nilson Silva]

Obter o Outlook para Android

Re: PYTHONPATH with cmake build

[stefanor]

Hi PICCA (2022.08.31_09:05:43_+)
> export PYBUILD_AFTER_BUILD=make -C {build_dir}/lib

I didn't do anything to support parallel, there. It may be nice to
(makes a huge difference to this package's build time).

> export PYBUILD_BEFORE_TEST=cp {build_dir}/lib/lib/*.so {build_dir}
> export PYBUILD_BEFORE_INSTALL=cp {build_dir}/lib/lib/*.so {build_dir}; rm -rf 
> {build_dir}/lib
> it seem to work but I am am not really confident with the 'rm -rf 
> {build_dir}/lib' during the install

I'd suggest an && instead of ; of course :)

And maybe logically, that should all happen in AFTER_BUILD...

> If I do not remove these files, they got installed by pybuild.

What's actually happening there is that they're getting installed by
setuptools. If we could install them into the right spot with cmake,
maybe we could reduce the copying and deleting. I didn't experiment with
that very much, just got to the point it worked...

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Re: PYTHONPATH with cmake build

[PICCA Frederic-Emmanuel]

Hello Stephano

I end up with this

#! /usr/bin/make -f 

export DH_VERSOBE=1

export PYBUILD_NAME=dxtbx 
export PYBUILD_SYSTEM=distutils
export PYBUILD_AFTER_CONFIGURE=cmake -DPython_EXECUTABLE=/usr/bin/{interpreter} 
-S . -B {build_dir}/lib
export PYBUILD_AFTER_BUILD=make -C {build_dir}/lib
export PYBUILD_BEFORE_TEST=cp {build_dir}/lib/lib/*.so {build_dir}
export PYBUILD_BEFORE_INSTALL=cp {build_dir}/lib/lib/*.so {build_dir}; rm -rf 
{build_dir}/lib

%:
dh $@ --with python3 --buildsystem=pybuild

override_dh_auto_test:  

it seem to work but I am am not really confident with the 'rm -rf 
{build_dir}/lib' during the install
If I do not remove these files, they got installed by pybuild.

no more magical obj-$blabla path :)


I now can concentrate on the unit test failures...

Cheers

Fred

Re: Lintian info message "hardening-no-bindnow" with vanilla debian/rules

[Julian Gilbey]

On Tue, Aug 30, 2022 at 07:33:07PM +0200, Gregor Riepl wrote:
> > I: python3-pyxdameraulevenshtein: hardening-no-bindnow 
> > [usr/lib/python3/dist-packages/pyxdameraulevenshtein.cpython-310-x86_64-linux-gnu.so]
> > 
> > and there is nothing about CFLAGS or the like in the setup.py file.
> > So if having this hardening flag enabled is a good thing, it should
> > probably be enabled somewhere within the pybuild system, rather than
> > every individual package with an extension file doing it.
> 
> Hardening is generally a good thing, but can break code in subtle ways.
> I suppose that's why it was decided that enabling it by default in Debian
> was deemed too risky.
> 
> Enabling it is quite easy, though: Just add
> 
> export DEB_BUILD_MAINT_OPTIONS = hardening=+all
> [...]

Thanks Gregor, I'll try that!

> Also, note that hardening-no-bindnow is an Informational message, so not
> strictly something that needs to be acted upon:
> https://lintian.debian.org/tags/hardening-no-bindnow

Indeed, hence the title of this message :-)

Best wishes,

   Julian