Difference between revisions of "Talk:Apertium on Windows"
(two replies) |
|||
| 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) |
||
:I'm sorry, but you're wrong. It's not possible to build Apertium with any currently existing version of Cygwin. Cygwin's great, but it's not 100%. Cygwin 1.7 reputedly has the missing pieces of Unicode support that we need, but it doesn't as yet use GCC 4, which we also need. As soon as Cygwin 1.7 is available with GCC 4, I'll look into it again. -- [[User:Jimregan|Jimregan]] 18:05, 22 November 2008 (UTC) |
|||
== Compilation == |
== Compilation == |
||
| Line 12: | Line 14: | ||
:All of the Windows stuff is now merged into the trunk. We should really delete the branch[es]. - [[User:Francis Tyers|Francis Tyers]] 12:51, 22 November 2008 (UTC) |
:All of the Windows stuff is now merged into the trunk. We should really delete the branch[es]. - [[User:Francis Tyers|Francis Tyers]] 12:51, 22 November 2008 (UTC) |
||
::Correction: the win32 work on lttoolbox has all been merged - it should build without problems in VC++. The work on Apertium hasn't all been merged, and it's not yet complete. I'll get to it, I'm just not majorly motivated, because I despise Windows :) -- [[User:Jimregan|Jimregan]] 18:05, 22 November 2008 (UTC) |
|||
Revision as of 18:05, 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)
- I'm sorry, but you're wrong. It's not possible to build Apertium with any currently existing version of Cygwin. Cygwin's great, but it's not 100%. Cygwin 1.7 reputedly has the missing pieces of Unicode support that we need, but it doesn't as yet use GCC 4, which we also need. As soon as Cygwin 1.7 is available with GCC 4, I'll look into it again. -- Jimregan 18:05, 22 November 2008 (UTC)
Compilation
Is "valgrind" the correct version to use for Windows ? But next, directory Win32 is missing, on the other hand "branches\apertium" has a Win32 dir. but no lttoolbox. The page can be updated depending on the answer.
- All of the Windows stuff is now merged into the trunk. We should really delete the branch[es]. - Francis Tyers 12:51, 22 November 2008 (UTC)
- Correction: the win32 work on lttoolbox has all been merged - it should build without problems in VC++. The work on Apertium hasn't all been merged, and it's not yet complete. I'll get to it, I'm just not majorly motivated, because I despise Windows :) -- Jimregan 18:05, 22 November 2008 (UTC)
