Hi Lumin,
Glad you are making progress.
A few more comments:
On 08/08/15 07:11, lumin wrote:
On Fri, 2015-08-07 at 11:24 +0100, Ghislain Vaillant wrote:
What are these packages supposed to contain ? Executables ? GUI apps ?
e.g.
caffe-cpu : some elf executables linked to libcaffe.so.0
libcaffe-cpu0 : libcaffe.so.0
libcaffe-cpu-dev : corresponding dev files
Another naming convention we use for these elf executables is to use
lib<name>-bin.
So according to the information your provided earlier, you could use:
libcaffe-bin or libcaffe-cpu-bin instead of caffe-cpu
and
libcaffe-cuda-bin instead of caffe-cuda
Choice is yours.
---
Another quick question for something I might have overlooked:
Is the cuda stuff really a different backend, i.e. it provides the exact
same functionalities as the CPU library [1] and can exist on its own?
or
does it enhance the CPU library with GPU-accelerated speedups for a
restricted subset of operations [2]?
In case of [1] use libcaffe-cpu / libcaffe-cuda
In case of [2] use libcaffe / libcaffe-cuda
Next I'm going to find a solution fixing nvcc compiling error
of caffe-cuda[1].
[1] https://github.com/BVLC/caffe/issues/2638
FYI, someone might have already mentioned this, but if your package
build-depends on any non-free stuff (like the cuda stack), your source
package will not qualify for inclusion in main but in contrib instead.
Ghis
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
