On Wed, Aug 17, 2011 at 15:28, Jelmer Vernooij <jel...@samba.org> wrote: > Which headers are necessary?
Here are the header files that are #included by winexe source files but which I couldn't find in the -dev packages. * includes.h = source4/include/includes.h * libcli/libcli.h = source4/libcli/libcli.h * libcli/raw/raw_proto.h = bin/default/source4/libcli/raw/raw_proto.h * libcli/resolve/resolve.h = source4/libcli/resolve/resolve.h * libcli/smb_composite/smb_composite.h = source4/libcli/smb_composite/smb_composite.h * lib/events/events.h = source4/lib/events/events.h * system/filesys.h = lib/replace/system/filesys.h These header files #include others. Results of a quick grep: #include "libcli/libcli_proto.h" #include "../libcli/nbt/libnbt.h" #include "libcli/raw/libcliraw.h" #include "libcli/raw/signing.h" #include "libcli/resolve/lp_proto.h" #include "libcli/resolve/proto.h" #include "libcli/smb2/smb2.h" #include "libcli/smb_composite/proto.h" #include "libcli/util/error.h" #include "librpc/gen_ndr/nbt.h" #include "../lib/util/attr.h" #include "../lib/util/debug.h" #include "../lib/util/safe_string.h" #include "../lib/util/smb_threads.h" #include "../lib/util/smb_threads_internal.h" #include "../lib/util/util.h" #include "../lib/util/xfile.h" #include "../replace/replace.h" #include "system/locale.h" #include "system/time.h" #include "system/wait.h" and these, in turn, will #include others.... > Alternatively, you should be able to use svcctl from Python rather than > from C. The svcctl python module is included in the python-samba package > already. Interesting idea! >> Given that winexe has to be built against the samba source tree, I >> think it's best if we try to get winexe included in Samba 4. >> > This doesn't seem likely given winexe is quite hard to build - it > requires mingw32. Building the winexesvc.exe Windows binary does require mingw (specifically, /usr/bin/i586-mingw32msvc-gcc and /usr/bin/amd64-mingw32msvc-gcc from the gcc-mingw32 package). Given that winexe would be the only component of Samba with this requirement, it would be sensible for upstream to make winexe an optional component, built conditionally upon waf being given "--with-winexe" or something like that. But this shouldn't be an issue for Debian which introduced gcc-mingw32 in squeeze. Are there any difficulties beyond that? Probably some things would have to be changed to follow Samba coding style, but that would not be much work. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
