Can be deleted: Difference between revisions
Joejoe2010 (talk | contribs) No edit summary |
Joejoe2010 (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
Furthermore we then would have to move the Windows installer from "InnoSetup" to "Nullsoft Install" as "Innosetup" does not run on Linux. | Furthermore we then would have to move the Windows installer from "InnoSetup" to "Nullsoft Install" as "Innosetup" does not run on Linux. | ||
A conversion tool can be found [http://nsis.sourceforge.net/Convert_Inno_Setup_scripts_to_NSIS_scripts here]. | |||
Another option would be using wine in order to run InnoSetup on Linux. This seems to be more complicated to me(Joachim) as there are several points where this way would fail. For example Xvfb (or ttydrv) would be needed as InnoSetup wants to use an X Window. | |||
It may work aswell but surely need more time for setting up and maintenancing it. | |||
More links: | More links: | ||
[http://stackoverflow.com/questions/7070358/creating-an-installer-via-command-line-through-jenkins-execute-batch-command installer on jenkins] | [http://stackoverflow.com/questions/7070358/creating-an-installer-via-command-line-through-jenkins-execute-batch-command installer on jenkins] | ||
Revision as of 20:11, 14 November 2011
It would be nice to hace a nightly build of the project (including all the installers) on Jenkins. In this it could also be part to get the po-files from launchpad.
By this, translators could work on a translation online and on the next day get an installer including already their translated items. This would it make easier for translators because then they can see their translations right away.
One option would be copying the po-files once a day to a launchpad-branch and then create a nant-task that copies the content of this branch into /i8n
See here
A nant command to get the po-files from a launchpad branch would be fe. <get src="http://nant.sourceforge.org/" dest="help/index.html" />
Furthermore we then would have to move the Windows installer from "InnoSetup" to "Nullsoft Install" as "Innosetup" does not run on Linux.
A conversion tool can be found here.
Another option would be using wine in order to run InnoSetup on Linux. This seems to be more complicated to me(Joachim) as there are several points where this way would fail. For example Xvfb (or ttydrv) would be needed as InnoSetup wants to use an X Window. It may work aswell but surely need more time for setting up and maintenancing it.
More links: installer on jenkins