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
Hi Andy,
That's how a properly written dev package is supposed to work. linuxcnc-dev
should solve all build dependencies. Some may argue disk usage, but you'd run
Gentoo instead of Debian if that was your concern.
Alec
On Sunday, May 23, 2021, 10:21:36 PM UTC, andy pugh wrote:
Is
> On 24 May 2021, at 8:19 am, 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"
I don't know but originally I thought
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"
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial
Hi,
I cleaned up my gtk3 branch. master-gtk3 on the official repo is now the
place to work on all gtk3 related changes.
https://github.com/LinuxCNC/linuxcnc/pull/1164
anything python3 related shoud go in master, unless it breaks something.
Please test it.
Rene
