Re: C++ and Python package combined

2018-04-10 Thread Nico Schlömer
Thanks Leo, If I interpret the build log [1] correctly, again the Python extension is build and linked with CMake, not `python setup.py install`. Also the package does some unusual trickery in assembling the setup.py file. Anyhow, thanks for the pointers. Cheers, Nico [1]

Re: C++ and Python package combined

2018-04-09 Thread Leopold Palomo-Avellaneda
Nico, On 09/04/18 15:13, Nico Schlömer wrote: > Thanks Leo, > > I've checked out ros-bond-core now and found that it's simpler than what I > have: The Python package is installed just like the rest of the library > with CMake, plus there are no compiled Python extensions that would need to >

Re: C++ and Python package combined

2018-04-09 Thread Nico Schlömer
Thanks Leo, I've checked out ros-bond-core now and found that it's simpler than what I have: The Python package is installed just like the rest of the library with CMake, plus there are no compiled Python extensions that would need to link against the bond library. That's why d/rules can be so

Re: C++ and Python package combined

2018-04-09 Thread Leopold Palomo-Avellaneda
On 06/04/18 16:38, Nico Schlömer wrote: > Hi everyone, > > I would like to package a piece of software that includes both a C++ > library and a Python package. When building locally from scratch, one is > supposed to > > * build and install the library first, > (* then build and run the

Re: C++ and Python package combined

2018-04-07 Thread Alex Mestiashvili
On 04/07/2018 10:43 AM, Nico Schlömer wrote: >> I guess you can set PKG_CONFIG_PATH and others appropriately. > > That sounds like what I got to do. I'm just figuring out which paths I need > exactly. Can I use export in d/rules? > > Cheers, > Nico You can find more examples of d/rules and all

Re: C++ and Python package combined

2018-04-07 Thread Georg Faerber
Hi, On 18-04-07 08:43:57, Nico Schlömer wrote: > > I guess you can set PKG_CONFIG_PATH and others appropriately. > > That sounds like what I got to do. I'm just figuring out which paths I > need exactly. Can I use export in d/rules? Yes, using export in d/rules works as expected. Cheers, Georg

Re: C++ and Python package combined

2018-04-07 Thread Paul Wise
On Sat, Apr 7, 2018 at 4:43 PM, Nico Schlömer wrote: > Can I use export in d/rules? I think so yes. -- bye, pabs https://wiki.debian.org/PaulWise

Re: C++ and Python package combined

2018-04-07 Thread Nico Schlömer
> I guess you can set PKG_CONFIG_PATH and others appropriately. That sounds like what I got to do. I'm just figuring out which paths I need exactly. Can I use export in d/rules? Cheers, Nico On Sat, Apr 7, 2018 at 10:24 AM Paul Wise wrote: > On Sat, Apr 7, 2018 at 4:04 PM,

Re: C++ and Python package combined

2018-04-07 Thread Paul Wise
On Sat, Apr 7, 2018 at 4:04 PM, Nico Schlömer wrote: >> Which software is this? > > FEniCS/Dolfin [1]. (I'm preparing the upcoming release.) Has something changed to prevent the existing dh overrides from working? https://sources.debian.org/src/dolfin/2017.2.0.post0-3/debian/rules > The latter

Re: C++ and Python package combined

2018-04-07 Thread Nico Schlömer
> Which software is this? FEniCS/Dolfin [1]. (I'm preparing the upcoming release.) > Does the upstream build system not take care of each of the steps? Like I said, upstream build instructions are: 1. Build and install the library. (Basically CMake + make install) 2. `cd python` and

Re: C++ and Python package combined

2018-04-07 Thread Paul Wise
On Fri, Apr 6, 2018 at 10:38 PM, Nico Schlömer wrote: > I would like to package a piece of software Which software is this? > Any hints? Does the upstream build system not take care of each of the steps? -- bye, pabs https://wiki.debian.org/PaulWise