Hallo Jeff,
thanks for the very detailed information.
I will see if I can understand it in a way being able to integrate the
GladeVCP widget.
The only files I am touching from linuxcnc are
configs/sim/gmoccapy/camview.glade
configs/sim/gmoccapy/gmoccapy_with_user_tabs.ini
lib/python/gladevcp/camview.py
lib/python/gladevcp/hal_python.xml
lib/python/gladevcp/hal_pythonplugin.py
Would it be also a posibility If I do check rom the code of camview.py,
if the needed depencies are satisfied and if not display a label instead
of the camera image telling the user to install the needed parts?
For me this way would be easier, but sure not the clean and beautifull way.
@Seb
I would like to have it in 2.7, as that one is the first nor working
well with the old camview. I know new features should go to master. But
I would like to help the actual users.
Norbert
Am 27.08.2016 um 16:01 schrieb Jeff Epler:
> Runtime dependencies that are constant for all platforms are listed in
> debian/control.{top,bottom}.in under the stanza for the related binary
> package.
>
> Runtime dependences that vary from platform to platform and are not
> autodetected by dpkg-buildpackage are listed in debian/configure. Right
> now this is only @KERNEL_HEADERS@, so this variable would need to be
> renamed or a new variable would need to be created and substituted.
>
> Compile-time dependencies are handled similarly, but in the very top
> stanza of debian/control.top.in.
>
> Optional features that some users want to install and others do not are
> best implemented via multiple binary packages, particularly if a large
> amount of disk space is used by the optional feature's dependencies.
> Creating a new binary package involves making a new Package stanza in
> debian/control.bottom.in and a new list of files to include in that
> binary package in debian/<subpackagename>.files or .files.in if
> substitution of @-variables is required. Perhaps an appropriate package
> name would be linuxcnc-camview.
>
> Optional features that don't even exist on all supported platforms would
> be done similarly to how (in master branch), debian/configure decides
> whether to include e.g., debian/control.uspace-rtai.in in the generated
> debian/control file.
>
> Of course, src/configure.in and src/Makefile "make install" support are
> also needed to get things in the right place for dpkg-buildpackage, as
> well as for RIP users.
>
> Jeff
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
------------------------------------------------------------------------------
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
