A `-dev` package is not meant satisfy dependencies for building the
packaged software, only the dependencies for other packages to build
*against* the packaged software. A `foo-dev` package might correspond
to a package `foo` containing a library `libfoo.so.1.2`, and the
`foo-dev` package should supply the headers, `libfoo.so.1` and
`libfoo.so` symlinks and any other dependencies to build against
`libfoo.so`. For example, `libfoo.so.1.2` may need `flex` and `bison`
to build, but other packages do not need those to build against `libfoo.so`.
Of course it's *possible* to replicate a source package's
`Build-Depends:` list in a binary package's `Depends:` list (`-dev` or
otherwise). Since the `linuxcnc-dev` package `Depends: linuxcnc`, I'd
worry about confusion created by having both an RIP build and a package
install on the same machine. Surprise may result from forgetting that
`$EMC_HOME` has been set or not. (Rene saw me fall for this one just in
the last week!) If this really must be done, it should be a completely
separate package that with no Depends: linuxcnc.
Better is simply to use the means provided by Debian developers to
automatically installing a source package's build dependencies; for
LinuxCNC, maybe:
sudo apt-get install devscripts
debian/configure uspace
mk-build-deps -irs sudo
Or if you have the LinuxCNC apt repos configured anyway:
apt-get build-dep linuxcnc
John
On 5/23/21 5:19 PM, andy pugh wrote:
Is there a good reason not to have all the build-time dependencies as
dependencies for linuxcnc-dev? This would mean that apt-get install
linuxcnc-dev would install all that is needed to run "make"
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
