[jitsi-dev] Jitsi installer on windows 64 and 32 bit


#1

Hi,

Can the jitsi maintaner for windows installer, share the environment details
that they are using (software package version numbers, dump the enviornemnt
variable values)

I am trying to build a jitsi installer and encountering some problems. I
hope the current jitsi package

Here is what I have documented and followed so far, what am I missing?

I am doing this all in a cygwin shell on windows 7.

Once I have everything running, I could convert following into a document
and upload somewhere. The idea is to produce a nice hands-on document.

Regards,
Adnan

1.Software requirements:
-cygwin

-mingw (only gcc, no g++) (used the installer zip file, noticed that
build.xml expect x86 and 64 directories to be sub-folders and to be used for
windows 32 bit and 64 bit respectively)

-make for win32 (make 3.8.1 in my case)

-wix35-binaries

-ant

-jdk1.6

2. PATH

In cygwin shell, put the bin directories of above software in the shell
PATH.

export PATH contains:

/cygdrive/c/mingw32/bin
/cygdrive/c/program files/ant/bin
/cygdrive/c/wix35-binaries
"/cygdrive/c/program files (x86)/Gnuwin32/bin" (path for Make)
/cygdrive/c/program files/java/jdk1.6.0_24/bin
/usr/bin
/usr/local/bin

···

-----------------------------------------------------------
3.CLASSPATH

Put the lib directory of the JDK into classpath

export CLASSPATH="/cygdrive/c/program files/java/jdk1.6.0_24/lib":.

For the rest we assume that ant build file would append suitable jitsi
directories to above.

4. Edit the build.xml and point to the JRE to be included in the installer
In a certain build file, change to the path to JRE to be installed alongwith
the jitsi (either point to a zipped jre or the actual directory)
grep for d:\jre you ll find it a default value.

5. Execute ant build script
Descend to jitsi root direcotry

ant build-installation-wix


#2

Hi
Can someone put prio on replying this? There are other user who have run
into problems..

http://java.net/nonav/projects/jitsi/lists/dev/archive/2011-05/message/163

http://comments.gmane.org/gmane.comp.voip.sip-communicator.devel/10768

/Adnan

···

On Mon, Jul 25, 2011 at 8:13 PM, Adnan <112linuxstockholm@gmail.com> wrote:

Hi,

Can the jitsi maintaner for windows installer, share the environment
details that they are using (software package version numbers, dump the
enviornemnt variable values)

I am trying to build a jitsi installer and encountering some problems. I
hope the current jitsi package

Here is what I have documented and followed so far, what am I missing?

I am doing this all in a cygwin shell on windows 7.

Once I have everything running, I could convert following into a document
and upload somewhere. The idea is to produce a nice hands-on document.

Regards,
Adnan

1.Software requirements:
-cygwin

-mingw (only gcc, no g++) (used the installer zip file, noticed that
build.xml expect x86 and 64 directories to be sub-folders and to be used for
windows 32 bit and 64 bit respectively)

-make for win32 (make 3.8.1 in my case)

-wix35-binaries

-ant

-jdk1.6

2. PATH

In cygwin shell, put the bin directories of above software in the shell
PATH.

export PATH contains:

/cygdrive/c/mingw32/bin
/cygdrive/c/program files/ant/bin
/cygdrive/c/wix35-binaries
"/cygdrive/c/program files (x86)/Gnuwin32/bin" (path for Make)
/cygdrive/c/program files/java/jdk1.6.0_24/bin
/usr/bin
/usr/local/bin
-----------------------------------------------------------
3.CLASSPATH

Put the lib directory of the JDK into classpath

export CLASSPATH="/cygdrive/c/program files/java/jdk1.6.0_24/lib":.

For the rest we assume that ant build file would append suitable jitsi
directories to above.

4. Edit the build.xml and point to the JRE to be included in the installer
In a certain build file, change to the path to JRE to be installed
alongwith the jitsi (either point to a zipped jre or the actual directory)
grep for d:\jre you ll find it a default value.

5. Execute ant build script
Descend to jitsi root direcotry

ant build-installation-wix


#3

The nightly Jitsi builds are working and have been doing so for quite
some time now even after build dependency updates. Additionally, I
have deployed or participated in the deployment of the build
dependencies on at least two machines while reading the relevant parts
of resources\install\build.xml and I have not encountered any problem.
Consequently and due to higher priorities, I am unlikely to have the
time to spend on this request in the near future. Anyway, you are
welcome to share your progress here for the benefit of the community.

···

On Wed, Jul 27, 2011 at 12:32 AM, Adnan <112linuxstockholm@gmail.com> wrote:

Can someone put prio on replying this?


#4

Hey

I now managed to create an installation binary on Windows-x86 (for x86) with the following steps and the attached patch.

@Lubo: The documentation in the build.xml is outdated and useless. Even more so since the pre-built run.exe is no longer included and the .msi is wrapped in an .exe. I have quite some dev-tools installed, but still had to modify my environment a lot. You should definitely try a build on a "virgin" (Windows) machine once you find some time.

win-makefiles.patch (3.88 KB)

···

---
download jre, put to d:\install (http://www.oracle.com/technetwork/java/javase/downloads/jre-6u26-download-400751.html)

create folder classes in resources\install
download mingw, install to c:\mingw\x86 (http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20110530/mingw-get-inst-20110530.exe/download)
copy mingw-make.exe to make.exe (directory c:\mingw\x86\bin)
add C:\MinGW\x86\bin to PATH

try whether you can run "make" in jitsi/src/native/windows/run
if it fails: either install cygwin or patch the makefiles

take care that WiX's binaries are located in c:\program files\wix (not in c:\program files\wix\bin), or change wix.home in the installer ant
the same modifications of run's makefile are also necessary in the cleansweep-make

download and install http://gnuwin32.sourceforge.net/downlinks/bzip2.php to c:\mingw\bzip2
download and install http://tukaani.org/xz/xz-5.0.3-windows.zip c:\mingw\xz

add env vars BZ2_HOME=c:\mingw\bzip2 and LZMA_HOME=C:\MinGW\xz

run the build-installation-wix target
---

Regards,
Ingo

-----Original Message-----
From: Lyubomir Marinov [mailto:lubo@sip-communicator.org] On Behalf Of
Lyubomir Marinov
Sent: Mittwoch, 27. Juli 2011 07:24
To: dev@jitsi.java.net
Cc: 112linuxstockholm@gmail.com
Subject: [jitsi-dev] Re: Jitsi installer on windows 64 and 32 bit
On Wed, Jul 27, 2011 at 12:32 AM, Adnan <112linuxstockholm@gmail.com> > wrote:

Can someone put prio on replying this?

The nightly Jitsi builds are working and have been doing so for quite
some time now even after build dependency updates. Additionally, I
have deployed or participated in the deployment of the build
dependencies on at least two machines while reading the relevant parts
of resources\install\build.xml and I have not encountered any problem.
Consequently and due to higher priorities, I am unlikely to have the
time to spend on this request in the near future. Anyway, you are
welcome to share your progress here for the benefit of the community.


#5

Thanks Bauersachs.

After Lyubomir's email, I felt like I am all alone and I dived into build
scripts and found that it is this bug http://www.mingw.org/node/45 that is
preventing the Makefile from getting compiled and thus failing the build.
Since Mingw can't handle inverted commas so on replacing them with ' or
removing them altogether, I got run.exe to be compiled.

I will go through what you have suggested and return with what worked for
me.
This sure can prevent others for wasting timing with such nitty gritties.

Cheers,
Adnan

···

On Wed, Jul 27, 2011 at 7:37 PM, Bauersachs Ingo <ingo.bauersachs@fhnw.ch>wrote:

Hey

I now managed to create an installation binary on Windows-x86 (for x86)
with the following steps and the attached patch.

@Lubo: The documentation in the build.xml is outdated and useless. Even
more so since the pre-built run.exe is no longer included and the .msi is
wrapped in an .exe. I have quite some dev-tools installed, but still had to
modify my environment a lot. You should definitely try a build on a "virgin"
(Windows) machine once you find some time.

---
download jre, put to d:\install (
http://www.oracle.com/technetwork/java/javase/downloads/jre-6u26-download-400751.html
)

create folder classes in resources\install
download mingw, install to c:\mingw\x86 (
http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/mingw-get-inst-20110530/mingw-get-inst-20110530.exe/download
)
copy mingw-make.exe to make.exe (directory c:\mingw\x86\bin)
add C:\MinGW\x86\bin to PATH

try whether you can run "make" in jitsi/src/native/windows/run
if it fails: either install cygwin or patch the makefiles

take care that WiX's binaries are located in c:\program files\wix (not in
c:\program files\wix\bin), or change wix.home in the installer ant
the same modifications of run's makefile are also necessary in the
cleansweep-make

download and install http://gnuwin32.sourceforge.net/downlinks/bzip2.phpto c:\mingw\bzip2
download and install http://tukaani.org/xz/xz-5.0.3-windows.zipc:\mingw\xz

add env vars BZ2_HOME=c:\mingw\bzip2 and LZMA_HOME=C:\MinGW\xz

run the build-installation-wix target
---

Regards,
Ingo

> -----Original Message-----
> From: Lyubomir Marinov [mailto:lubo@sip-communicator.org] On Behalf Of
> Lyubomir Marinov
> Sent: Mittwoch, 27. Juli 2011 07:24
> To: dev@jitsi.java.net
> Cc: 112linuxstockholm@gmail.com
> Subject: [jitsi-dev] Re: Jitsi installer on windows 64 and 32 bit
> On Wed, Jul 27, 2011 at 12:32 AM, Adnan <112linuxstockholm@gmail.com> > > wrote:
>> Can someone put prio on replying this?
>
> The nightly Jitsi builds are working and have been doing so for quite
> some time now even after build dependency updates. Additionally, I
> have deployed or participated in the deployment of the build
> dependencies on at least two machines while reading the relevant parts
> of resources\install\build.xml and I have not encountered any problem.
> Consequently and due to higher priorities, I am unlikely to have the
> time to spend on this request in the near future. Anyway, you are
> welcome to share your progress here for the benefit of the community.


#6

Hey

After Lyubomir's email, I felt like I am all alone and I dived into build
scripts and found that it is this bug http://www.mingw.org/node/45 that is
preventing the Makefile from getting compiled and thus failing the build.
Since Mingw can't handle inverted commas so on replacing them with ' or
removing them altogether, I got run.exe to be compiled.

I tried without Cygwin, so we have probably different environments. And I only tried to generate the setup, I didn't try to generate the usually pre-built native libraries that are used via JNI. I can only image what's needed to get them all compiled...

Thanks for your (promised :-)) documentation effort!

Regards,
Ingo


#7

Hi,

Last week, the same day I received your email, I followed your procedure on
my 64 bit windows vista. I experienced problems with the gcc, unable to
compile cleansweep.exe,etc.

If the currente maintaner can list what packages are they using and which
version that could save time.

I am on vaccation now.

Regards,
Adnan

···

On Wed, Jul 27, 2011 at 9:07 PM, Bauersachs Ingo <ingo.bauersachs@fhnw.ch>wrote:

Hey

> After Lyubomir's email, I felt like I am all alone and I dived into build
> scripts and found that it is this bug http://www.mingw.org/node/45 that
is
> preventing the Makefile from getting compiled and thus failing the build.
> Since Mingw can't handle inverted commas so on replacing them with ' or
> removing them altogether, I got run.exe to be compiled.

I tried without Cygwin, so we have probably different environments. And I
only tried to generate the setup, I didn't try to generate the usually
pre-built native libraries that are used via JNI. I can only image what's
needed to get them all compiled...

Thanks for your (promised :-)) documentation effort!

Regards,
Ingo


#8

Hey

Last week, the same day I received your email, I followed your procedure
on my 64 bit windows vista. I experienced problems with the gcc, unable to
compile cleansweep.exe,etc.

Please post the error messages you get. The required libraries for run.exe, cleansweep.exe and setup.exe were all included in my description. I doubt that there are much differences between x86 and x64.

Regards,
Ingo