On 23/09/14 11:19, Martin Lucina wrote: > Will do and thanks for your work. This will be a nice experiment for me > and if I end up needing to port the application to Windows (which may well > happen later) then I can at least contribute that work back to > rumpkernel.org.
Do you mean "port to windows" as in "win32" or "cygwin"? It would be interesting to hear about experiences with the former. You'll need to at least add a cdefs_pecoff.h to the NetBSD sources (see sys/cdefs.h) to cope with the different object file format that Windows uses. With the build system for win32 you're on your own ;) When playing around with cygwin, I had some trouble with weak symbols, but maybe it was a cygwin toolchain issue, and besides, we've since then radically reduced weak symbols in rump kernels (they caused problems with e.g. glibc and others), so maybe that problem has just gone away. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
