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]
https://buildd.debian.o
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
> link
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 sim
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 tests
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 o
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
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
> 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, Nico Schlömer wrote:
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
> 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 insta
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
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 tests, compiling against what just has been
installed,)
* t
12 matches
Mail list logo
