[Kst] cmake for pykst

[Steve Benton]

On 11-11-16 12:14 PM, Barth Netterfield wrote:
> cmake for pykst is really cool!  I love the auto down-load/install for
> numpy and scipy!
>
> Some comments:
> It doesn't seem to check to see if you already have numpy/scipy
> installed.  Can/should we do that check?
Certainly if the user has a sufficiently new version installed (from a
package or otherwise) nothing new should be installed. It's more
complicated when somebody has numpy/scipy that are not compatible with
pykst. For that case, there must be some way for different versions of a
python module to peacefully coexist on a system. (I don't know what it
is though.)
> Do people think that pykst should be installed with kst, or should it
> be a separate package?
I have no problem with pykst being bundled with the kst source. Or not.
The debian/ubuntu/etc binary package will have to be separate (probably
for fedora/etc too), but you don't need to worry about that.
> I was also a little surprised by how it worked.
>
> By analogy to what kst does, I expected
>   [pykst_build$] cmake ../cmake/pykst
> to create pykstpp_h.py and put it (and maybe the other source files)
> in a subdir (./src?)
>
> I don't know what to expect from
>   [pykst_build$] make
>
> I expected
>   [pykst_build$] sudo make install
> to copy all of the py files to the correct python directory
>
> I think that installing the dependencies maybe should be done by
>   [pykst_build$] sudo make deps
> or something like that, rather than make.  Or is it already a cmake
> option? (download 3rd party)?
>
> But I really don't know.  Can the packagers (Steve?  Matt?) comment on this?
I know very little about cmake. For my packages I just used a CDBS
script that does standard cmake building and installation. Maybe the
official debian package does something more fancy.