Difference between revisions of "Talk:Apertium on Windows"
| Line 6: | Line 6: | ||
It should be possible, but cygwin distribution must be optimized for size. I've tried compiling apertium with cygwin last week, but it gave some errors and could not advance further. I would also appreciate if someone had packaged cygwin with apertium and also supplied a batch file which enables translation with a simple double click under Windows environment.--[[User:Msalperen|Msalperen]] 09:14, 10 November 2007 (UTC) |
It should be possible, but cygwin distribution must be optimized for size. I've tried compiling apertium with cygwin last week, but it gave some errors and could not advance further. I would also appreciate if someone had packaged cygwin with apertium and also supplied a batch file which enables translation with a simple double click under Windows environment.--[[User:Msalperen|Msalperen]] 09:14, 10 November 2007 (UTC) |
||
== Compilation == |
|||
Is "valgrind" the correct version to use for Windows ? But next, directory Win32 is missing, on the other hand "branches\apertium\win32" has a Win32 but no lttoolbox. The page can be updated depending on the answer. |
|||
Revision as of 12:16, 22 November 2008
Packaging a windows release?
Perhaps Cygwin license[1] would allow a packging of apertium and the required cygwin items to create a windows release?
Ote 22:55, 9 November 2007 (UTC)
It should be possible, but cygwin distribution must be optimized for size. I've tried compiling apertium with cygwin last week, but it gave some errors and could not advance further. I would also appreciate if someone had packaged cygwin with apertium and also supplied a batch file which enables translation with a simple double click under Windows environment.--Msalperen 09:14, 10 November 2007 (UTC)
Compilation
Is "valgrind" the correct version to use for Windows ? But next, directory Win32 is missing, on the other hand "branches\apertium\win32" has a Win32 but no lttoolbox. The page can be updated depending on the answer.
