请向我们提供有关您的申请的更多信息。 简单的命令行实用程序？ 使用 KDE 库？ 使用 Linux 内核扩展？ 等等等等。仅供内部使用？ 用于企业桌面？ 供最终用户使用？ 这些都会改变我们的建议。
我还建议使用 MinGW。
移植的基本过程：
安装MinGW和MSYS
运行你的Makefile。
您可能会收到错误，请修复它（通过更改代码或将其注释掉）
通过 Makefile 重新编译。
重复2-4，直到编译没有错误。
然后测试您的应用程序，并跟踪您可能引入的任何错误。
Please give us more information about your application. Simple commandline utility? Uses KDE libraries? Uses linux kernel extensions? etc etc. For internal use only? For use on corporate desktops? For use by end-users? These all will change our suggestions.
I'll also suggest using MinGW.
The basic process of porting:
Install MinGW and MSYS
Run your Makefile.
Likely you'll get an error, fix it (either by changing code or by commenting it out)
Recompile via Makefile.
Repeat 2-4 until you compile with no errors.
Then test your application, and track down any bugs you might have introduced.
I am by no means an expert. Saying that, if you're not going to release your application, I believe you can use it with GPL'd stuff internally. It is only when you started distributing your binaries that you are bound by the GPL to release your source along with the binary, or by user request. E.g. a company could modify some GPL'd source code, and use it internally so long as they don't distribute the code or application outside of the company.
So it depends on what you plan to do with your app.
You might be able to use cygwin for now just to get it to a working point, and then gradually replace pieces of the app with native windows code until you've completely de-cygwin'd it.
I know that's probably not what you're looking form, but I thought I'd throw that out there. They should have a couple law/licensing classes shoved into CS degrees these days.
发布评论
评论（4）
MinGW 没有像 Cygwin 那样多的许可限制，但可能需要付出更多努力才能让您的代码跑在它下面。
MinGW doesn't have as many licensing restrictions as Cygwin, but it might require more effort to get your code to run under it.
请向我们提供有关您的申请的更多信息。 简单的命令行实用程序？ 使用 KDE 库？ 使用 Linux 内核扩展？ 等等等等。仅供内部使用？ 用于企业桌面？ 供最终用户使用？ 这些都会改变我们的建议。
我还建议使用 MinGW。
移植的基本过程：
Please give us more information about your application. Simple commandline utility? Uses KDE libraries? Uses linux kernel extensions? etc etc. For internal use only? For use on corporate desktops? For use by end-users? These all will change our suggestions.
I'll also suggest using MinGW.
The basic process of porting:
我绝不是专家。 也就是说，如果您不打算发布您的应用程序，我相信您可以在内部将其与 GPL 的东西一起使用。 只有当您开始分发二进制文件时，您才受 GPL 约束，必须随二进制文件一起发布源代码，或者根据用户请求发布源代码。 例如公司可以修改一些 GPL 源代码，并在内部使用它，只要他们不将代码或应用程序分发到公司外部即可。
所以这取决于您打算用您的应用程序做什么。
您现在也许可以使用 cygwin 只是为了让它达到工作点，然后逐渐用本机 Windows 代码替换应用程序的各个部分，直到完全取消 cygwin。
我知道这可能不是你想要的形式，但我想我应该把它扔掉。 如今，他们应该将一些法律/许可课程推入计算机科学学位。
I am by no means an expert. Saying that, if you're not going to release your application, I believe you can use it with GPL'd stuff internally. It is only when you started distributing your binaries that you are bound by the GPL to release your source along with the binary, or by user request. E.g. a company could modify some GPL'd source code, and use it internally so long as they don't distribute the code or application outside of the company.
So it depends on what you plan to do with your app.
You might be able to use cygwin for now just to get it to a working point, and then gradually replace pieces of the app with native windows code until you've completely de-cygwin'd it.
I know that's probably not what you're looking form, but I thought I'd throw that out there. They should have a couple law/licensing classes shoved into CS degrees these days.
Cygwin 还有一个商业许可证。
http://www.redhat.com/services/custom/cygwin/
There is also a commercial license for Cygwin.
http://www.redhat.com/services/custom/cygwin/