Am Donnerstag, den 30.07.2009, 21:08 +0200 schrieb Damien Sandras:
Hi Michael,
First of all, thanks for the continuous work. I think your efforts will
lead to a more stable Ekiga.
After examinating the logs, I think we can first try fixing the crash.
We can fix the deadlock after.
When
Damien Sandras schrieb:
I hope that you have really enjoing holidays, Damien. But to keep the
others informed, the Vista stuff is really nagging for me. I think that
I spotted the reason for the crash under Vista-SP2 in ptlib and filed a
bug at
Hello,
I continue working on win32 version.
The last version of ekiga. exe is available at
http://www.pateam.org/archive/tmp/ekiga-win32/trunk/
(http://www.pateam.org/archive/tmp/ekiga-win32/trunk/ekiga-setup-3.3.1-git-302_g5d4151a.exe)
with the related Makefile.
I've done different tests
Thierry Simonnet schrieb:
Hello,
I continue working on win32 version.
The last version of ekiga. exe is available at
http://www.pateam.org/archive/tmp/ekiga-win32/trunk/
(http://www.pateam.org/archive/tmp/ekiga-win32/trunk/ekiga-setup-3.3.1-git-302_g5d4151a.exe)
with the related Makefile.
Michael Rickmann wrote:
Thierry Simonnet schrieb:
Hello,
I continue working on win32 version.
The last version of ekiga. exe is available at
http://www.pateam.org/archive/tmp/ekiga-win32/trunk/
(http://www.pateam.org/archive/tmp/ekiga-win32/trunk/ekiga-setup-3.3.1-git-302_g5d4151a.exe)
Damien Sandras schrieb:
Le mercredi 22 juillet 2009 à 23:22 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le mercredi 22 juillet 2009 à 19:49 +0200, Michael Rickmann a écrit :
I have a Vista notebook available for three days only. As already
reported Ekiga has to be killed at
Hello,
I've done more tests using git-302 version :
I ve the following message when enabling audio input :
-
Error while opening audio output device SoundMax HD audio
Only silence will be transmitted.
The selected audio device was successfully opened but it is
I suppose your sound card is not supported by alsa or by ptlib?? Could
you send the -d 4 output? It should contain more information about the
error.
Eugen
Thierry Simonnet wrote:
Hello,
I've done more tests using git-302 version :
I ve the following message when enabling audio input :
Hello,
it is now possible to have a version of Ekiga for windows.
I noticed with the last trunk version (this morning) I can't activate
any iaudio input. I can call without trouble but only if audio input is
on SILENT. I tested it with a camera with mic and with a camera without
mic.
Ringing
Thierry Simonnet wrote:
Hello,
it is now possible to have a version of Ekiga for windows.
I noticed with the last trunk version (this morning) I can't activate
any iaudio input. I can call without trouble but only if audio input is
on SILENT. I tested it with a camera with mic and with a
Le mercredi 22 juillet 2009 à 23:22 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le mercredi 22 juillet 2009 à 19:49 +0200, Michael Rickmann a écrit :
I have a Vista notebook available for three days only. As already
reported Ekiga has to be killed at shutdown. It seems a
I have a Vista notebook available for three days only. As already
reported Ekiga has to be killed at shutdown. It seems a pecularity of
Vista which can be overcome by several means.
if (Vista)
1) Wait at the end of the main thread ca. 5 secs, or
2) do Wait 100 msec, enumerate Ekiga's threads
Le mercredi 22 juillet 2009 à 19:49 +0200, Michael Rickmann a écrit :
I have a Vista notebook available for three days only. As already
reported Ekiga has to be killed at shutdown. It seems a pecularity of
Vista which can be overcome by several means.
if (Vista)
1) Wait at the end of the
Damien Sandras schrieb:
Le mercredi 22 juillet 2009 à 19:49 +0200, Michael Rickmann a écrit :
I have a Vista notebook available for three days only. As already
reported Ekiga has to be killed at shutdown. It seems a pecularity of
Vista which can be overcome by several means.
if (Vista)
1)
Am Samstag, den 18.07.2009, 21:54 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga's handling of Windows file names and device names is done mostly
in UTF-8 which works as long as there are no national characters in the
names. I have a German Windows and a USB headset which in
Michael Rickmann wrote:
Am Samstag, den 18.07.2009, 21:54 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga's handling of Windows file names and device names is done mostly
in UTF-8 which works as long as there are no national characters in the
names. I have a German Windows and a USB
Eugen Dedu wrote:
Michael Rickmann wrote:
Am Samstag, den 18.07.2009, 21:54 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga's handling of Windows file names and device names is done
mostly in UTF-8 which works as long as there are no national
characters in the names. I have a German
Michael Rickmann wrote:
Ekiga's handling of Windows file names and device names is done mostly
in UTF-8 which works as long as there are no national characters in the
names. I have a German Windows and a USB headset which in Ekiga shows up
as USB-Ger instead of USB-Gerät (USB device). Ok, I
Michael Rickmann wrote:
I am trying to prepare a Win32 version of Ekiga 3.2.5 for ekiga.org and
realized that I had to pick a few items from Opal HEAD and Ekiga master.
For Ekiga I think that the following Win32 commits are safe to be merged
into stable from where they can be picked up for the
Michael Rickmann wrote:
Ekiga's handling of Windows file names and device names is done mostly
in UTF-8 which works as long as there are no national characters in the
names. I have a German Windows and a USB headset which in Ekiga shows up
as USB-Ger instead of USB-Gerät (USB device). Ok, I
Damien Sandras schrieb:
Michael,
Le mercredi 15 juillet 2009 à 21:47 +0200, Michael Rickmann a écrit :
[...]
[...]
This patch should fix the problem:
http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=revrevision=23106
However, I'm not sure any patch is still required in Ekiga.
In
Ekiga's handling of Windows file names and device names is done mostly
in UTF-8 which works as long as there are no national characters in the
names. I have a German Windows and a USB headset which in Ekiga shows up
as USB-Ger instead of USB-Gerät (USB device). Ok, I can click
Ekiga's update
I am trying to prepare a Win32 version of Ekiga 3.2.5 for ekiga.org and
realized that I had to pick a few items from Opal HEAD and Ekiga master.
For Ekiga I think that the following Win32 commits are safe to be merged
into stable from where they can be picked up for the next release.
available at http://wwwuser.gwdg.de/~mrickma/ekiga/ . They are the files
containing 3.2.5 . I think that is about what I can achieve at the
moment. Refinements will follow. Please test!! If you do not have
Windows, free some 30 -50G partition on one of your disks, google for
Windows 7 (I think
Le mercredi 15 juillet 2009 à 21:47 +0200, Michael Rickmann a écrit :
[...]
Could you make sure whether the interpretation of the new API to read as
many buffers to fullfill the size arggument of PBoolean
OpalRawMediaStream::ReadData(BYTE * buffer, PINDEX size, PINDEX
length) is correct?
Michael,
Le mercredi 15 juillet 2009 à 21:47 +0200, Michael Rickmann a écrit :
[...]
Well it all condenses down to line opal-3.6.4/src/opal/patch.cxx:217
which is
source.SetDataSize(sink-primaryCodec-GetOptimalDataFrameSize(true),
sourceFormat.GetFrameSize());
Opal's ***dataSize***,
Damien Sandras schrieb:
Michael,
Le mercredi 15 juillet 2009 à 21:47 +0200, Michael Rickmann a écrit :
[...]
Well it all condenses down to line opal-3.6.4/src/opal/patch.cxx:217
which is
source.SetDataSize(sink-primaryCodec-GetOptimalDataFrameSize(true),
sourceFormat.GetFrameSize());
Opal's
Am Dienstag, den 14.07.2009, 23:09 +0200 schrieb Damien Sandras:
Le mardi 14 juillet 2009 à 18:06 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40
Le mercredi 15 juillet 2009 à 08:52 +0200, Michael Rickmann a écrit :
Am Dienstag, den 14.07.2009, 23:09 +0200 schrieb Damien Sandras:
Le mardi 14 juillet 2009 à 18:06 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows
Damien Sandras schrieb:
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been
Le mardi 14 juillet 2009 à 18:06 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le lundi 13 juillet 2009 à 23:32 +0200, Michael Rickmann a écrit :
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and rendered WinXP and Win7 unusable. Today I found the reason: commit
23036
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and rendered WinXP and Win7 unusable. Today I found the reason: commit
23036
Am Montag, den 13.07.2009, 16:01 +0200 schrieb Damien Sandras:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and
Damien Sandras schrieb:
Le dimanche 12 juillet 2009 à 22:40 +0200, Michael Rickmann a écrit :
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and rendered WinXP and Win7 unusable. Today I found the
I was stuck testing the latest changes to Ekiga since about 10 days.
Once a call to 5...@ekiga.net had been established windows were piling up
and rendered WinXP and Win7 unusable. Today I found the reason: commit
23036 to opal trunk which coresponds to 23028 opal v3_6 and is
contained in
Michael Rickmann a écrit :
Hello everybody,
I have a new Windows version of Ekiga head based on attached minimal but
rather effective patches. you find it in my directory at
http://wwwuser.gwdg.de/~mrickma/ekiga/ . As to the patches:
1) ekiga_linkmagic.diff : It allows the linker to chose
Julien Puydt a écrit :
Julien Puydt a écrit :
- I couldn't call 5...@ekiga.net ; or more precisely, I asked to place
the call and ended up with an ekiga which wasn't really in a call, and
wasn't really off a call (it would only allow me to Hang up but that
wouldn't do anything).
Eh, I just
Michael Rickmann a écrit :
Hello everybody,
I have a new Windows version of Ekiga head based on attached minimal
but rather effective patches. you find it in my directory at
http://wwwuser.gwdg.de/~mrickma/ekiga/ . As to the patches:
1) ekiga_linkmagic.diff : It allows the linker to chose
Am Mittwoch, den 29.04.2009, 11:35 +0200 schrieb Thierry Simonnet:
Hi,
I'm just back to my office after several weeks and I saw that a lot of
things have changed.
I modified Makefile to handle git, gtk2.16, opal/trunk, ptlib/trunk
(in attachment).
I tried to compile Ekiga for win32
Hi Craig,
If upstream means Opal, then I think this is being a bit unfair.
I use Opal/PTLib on Windows and Linux every day. On both these operating
systems, there is no problem.
We are extremely busy maintaining support for these two operating systems
using their native compilers (gcc and
Am Mittwoch, den 29.04.2009, 11:35 +0200 schrieb Thierry Simonnet:
Hi,
I'm just back to my office after several weeks and I saw that a lot of
things have changed.
I modified Makefile to handle git, gtk2.16, opal/trunk, ptlib/trunk
(in attachment).
I tried to compile Ekiga for win32
Hi,
I'm just back to my office after several weeks and I saw that a lot of
things have changed.
I modified Makefile to handle git, gtk2.16, opal/trunk, ptlib/trunk
(in attachment).
I tried to compile Ekiga for win32 using Debian Lenny 32b and 64b. Here
are the outputs :
32b :
Craig Southeren wrote:
Now, if I could cross-compile ekiga on a Fedora box then I would be
REALLY interested. :)
The official build on ekiga.net is from a Fedora box. I made that build
on Fedora 10.
yum install mingw32-gcc
___
Michael Cronenworth wrote:
Craig Southeren wrote:
Now, if I could cross-compile ekiga on a Fedora box then I would be
REALLY interested. :)
The official build on ekiga.net is from a Fedora box. I made that build
on Fedora 10.
yum install mingw32-gcc
Last time I tried the procedure
Craig Southeren wrote:
Last time I tried the procedure at the following URL, it didn't even
go close to working on Fedora:
http://wiki.ekiga.org/index.php/Cross-compile_Win32
Is that this what you did? Were any changes needed?
The Makefile in Gnome SVN/Git is not appropriate for Fedora
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html .
At the moment I work with Ubuntu Intrepid on git master and get circular
inclusion of uuids.h and ksuuids.h
Michael Rickmann wrote:
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html .
At the moment I work with Ubuntu Intrepid on git master and get circular
inclusion of
Michael Rickmann a écrit :
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html .
At the moment I work with Ubuntu Intrepid on git master and get circular
inclusion
Am Sonntag, den 26.04.2009, 15:31 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html
. At the moment I
Michael Rickmann wrote:
Am Sonntag, den 26.04.2009, 15:31 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
http://mail.gnome.org/archives/ekiga-devel-list/2009-February/msg00042.html .
Am Sonntag, den 26.04.2009, 17:00 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Am Sonntag, den 26.04.2009, 15:31 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in February:
Michael Rickmann wrote:
Am Sonntag, den 26.04.2009, 17:00 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Am Sonntag, den 26.04.2009, 15:31 +0200 schrieb Eugen Dedu:
Michael Rickmann wrote:
Ekiga SVN commit 7653 seems not complete. It is apparently based on a
discussion on this list in
Michael Rickmann a écrit :
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major issues: Where does
Julien Puydt a écrit :
Michael Rickmann a écrit :
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major
Michael Rickmann wrote:
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major issues: Where does
Building Win32 Ekiga from current heads is not straightforward. Ekiga,
Ptlib and Opal seem to have regressed in some aspects.
1) In Ekiga videooutput-manager-dx.cpp can not be compiled. I tried to
fix it with attached patch. There were two major issues: Where does
GMVideoDisplay_DX come from? I
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detailaid=2728003group_id=204472atid=989748
https://sourceforge.net/tracker/?func=detailaid=2728037group_id=204472atid=989748
Another Win32 issue, the crash on exit one: I have been fighting to
obtain a debug built of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Rickmann a écrit :
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detailaid=2728003group_id=204472atid=989748
https://sourceforge.net/tracker/?func=detailaid=2728037group_id=204472atid=989748
Another Win32
Michael Rickmann wrote:
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detailaid=2728003group_id=204472atid=989748
https://sourceforge.net/tracker/?func=detailaid=2728037group_id=204472atid=989748
Another Win32 issue, the crash on exit one: I have been fighting
Eugen Dedu a écrit :
Michael Rickmann wrote:
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detailaid=2728003group_id=204472atid=989748
https://sourceforge.net/tracker/?func=detailaid=2728037group_id=204472atid=989748
Another Win32 issue, the crash on exit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Puydt a écrit :
Julien Puydt a écrit :
Oh, yes, I know that bug... but I still haven't understood it... and
the fact that I can't reproduce it doesn't help (I get other
crashes... in ptlib/opal).
I got an idea and pushed a would-be
yannick a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Julien Puydt a écrit :
Julien Puydt a écrit :
Oh, yes, I know that bug... but I still haven't understood it... and
the fact that I can't reproduce it doesn't help (I get other
crashes... in ptlib/opal).
I got an idea and pushed
Ok I have submitted the two bug reports
https://sourceforge.net/tracker/?func=detailaid=2728003group_id=204472atid=989748
https://sourceforge.net/tracker/?func=detailaid=2728037group_id=204472atid=989748
Another Win32 issue, the crash on exit one: I have been fighting to
There is people
Michael Rickmann wrote:
I just joined back into this list again. I tried to cross compile ekiga
for win32. I was a bit lost what all these branches and tags are meant
for. So I took trunk for ekiga, tag v3_6_1 for opal and tag v2_6_1 for
Very well explained at http://wiki.ekiga.org, section
Michael Rickmann a écrit :
I made a preliminary patch to ekiga/configure.ac which allows
configuration --with-libsasl2-dir=$(LIBSASL2_DIR), see attachment. This
allows Ekiga to be compiled with ldap support.
Applied, thanks!
Snarj
___
Le mercredi 18 février 2009 à 18:32 +0100, Damien Sandras a écrit :
Le lundi 16 février 2009 à 12:49 +0100, Thierry Simonnet a écrit :
Here are some patches and procedure I followed :
* I change Makefile and especially some URL due to server
failure.
* patch contain.h
Damien Sandras wrote:
Le mercredi 18 février 2009 à 18:32 +0100, Damien Sandras a écrit :
Le lundi 16 février 2009 à 12:49 +0100, Thierry Simonnet a écrit :
Here are some patches and procedure I followed :
* I change Makefile and especially some URL due to server
failure.
I compiled last svn version (7672).
Here is the result of cross compile :
/usr/lib/gcc/i586-mingw32msvc/4.2.1-sjlj/../../../../i586-mingw32msvc/bin/ld:
warning: auto-importing has been activated without --enable-auto-import
specified on the command line.
This should work unless it involves
Le mercredi 18 février 2009 à 14:53 +0100, Thierry Simonnet a écrit :
I compiled last svn version (7672).
Here is the result of cross compile :
/usr/lib/gcc/i586-mingw32msvc/4.2.1-sjlj/../../../../i586-mingw32msvc/bin/ld:
warning: auto-importing has been activated without
Here are some patches and procedure I followed :
I change Makefile and especially some URL due to server failure.
patch contain.h
patch ptime.cxx
rm -r src/opal/plugins/audio/G722/
rm -r opal/plugins/audio/G722/
src/ekiga/lib/platform/platform-win32.c seems to be OK now (line
Here are some patches and procedure I followed :
I change Makefile and especially some URL due to server failure.
patch contain.h
patch ptime.cxx
rm -r src/opal/plugins/audio/G722/
rm -r opal/plugins/audio/G722/
src/ekiga/lib/platform/platform-win32.c seems to be OK now (line
More feedback :
As I have no debug output using win32 version, linux version gave me :
(ekiga:31062): GLib-GObject-WARNING **: invalid cast from `GtkDialog' to
`NotifyNotification'
(ekiga:31062): libnotify-CRITICAL **: notify_notification_close:
assertion
A modified Makefile and a binary of ekiga 3.1.x
(ekiga-setup-3.1_7661.exe) is available at
http://www.pateam.org/archive/tmp/ekiga-win32/trunk/
Please let me know if you have any trouble using it.
Makefile has wget --no-proxy option removed.
Best regards
Thierry Simonnet wrote:
I succeded
Le dimanche 15 février 2009 à 14:18 +0100, Thierry Simonnet a écrit :
A modified Makefile and a binary of ekiga 3.1.x
(ekiga-setup-3.1_7661.exe) is available at
http://www.pateam.org/archive/tmp/ekiga-win32/trunk/
Please let me know if you have any trouble using it.
Makefile has wget
I will do all of them today and give you some feedback on .exe under
win XP.
I also inted to work on G722 (doesn't compile with mingw), ldap
integration and DEBUG option.
Damien Sandras wrote:
Le dimanche 15 février 2009 à 14:18 +0100, Thierry Simonnet a écrit :
A modified
I succeded to have an Ekiga win32 exe using trunk branch of svn.
I followed wiki instruction for cross compiling (packages...)
mingw32 version : 4.2.1
Then some minor modifications :
Win32 Makefile :
Opal version : 3.5.2
PTLib version : 2.5.2
unable to use DEBUG. In fact
Thierry Simonnet wrote:
Is anybody have an idea?
I had to do the same thing. I'm putting together a compilation of
problems I've encountered with cross-compiling on Fedora, which seems to
be using updated packages of mingw32 stuff. I have a working build and
will be creating a new e-mail
Hello,
I will attempt to build the Win32 package for you guys, but first I'd
like to know if there is any place where I can grab the NSIS installer
script or the list of packages that were used during compiling. I can
fair enough on my own to build it, but I'd like to match the feature set
yannick wrote:
The guy who made the windows package wrote this:
http://wiki.ekiga.org/index.php/Cross-compile_Win32_3.0
Ah... Fedora is now including mingw as well. :)
I'll put in a request for a wiki account. Thanks.
___
Ekiga-devel-list
Le mercredi 12 novembre 2008 à 14:07 +, Matthias Schneider a écrit :
Hi all,
is there some more feedback on the latest win32 build available? The only
thing that was brought to my attention was that there is a console being
opened with some debug information spit out. If thats all
Hi all,
is there some more feedback on the latest win32 build available? The only
thing that was brought to my attention was that there is a console being
opened with some debug information spit out. If thats all trouble that ekiga
for windows is having I thing we are doing quite
Hi all,
is there some more feedback on the latest win32 build available? The only thing
that was brought to my attention was that there is a console being opened with
some debug information spit out. If thats all trouble that ekiga for windows is
having I thing we are doing quite alright...
Le mercredi 12 novembre 2008 à 14:07 +, Matthias Schneider a écrit :
Hi all,
is there some more feedback on the latest win32 build available? The only
thing that was brought to my attention was that there is a console being
opened with some debug information spit out. If thats all
is not released yet? Anyway its just cosmetics...
Regards,
Torsten
Original-Nachricht
Datum: Sun, 13 Apr 2008 10:22:33 +0200
Von: Matthias Schneider [EMAIL PROTECTED]
An: Ekiga development mailing list ekiga-devel-list@gnome.org
Betreff: [Ekiga-devel-list] win32 build
Hi Torsten
2008 10:22:33 +0200
Von: Matthias Schneider [EMAIL PROTECTED]
An: Ekiga development mailing list ekiga-devel-list@gnome.org
Betreff: [Ekiga-devel-list] win32 build
Hi Torsten,
the win32 build has been fixed. In order to verify your build environment,
you
can try the following patch
Schneider [EMAIL PROTECTED]
An: Ekiga development mailing list ekiga-devel-list@gnome.org
Betreff: [Ekiga-devel-list] win32 build
Hi Torsten,
the win32 build has been fixed. In order to verify your build environment,
you
can try the following patch to switch to my reference revisions
Hi Torsten,
the win32 build has been fixed. In order to verify your build environment, you
can try the following patch to switch to my reference revisions which I have
tested.
There are two issues that might appear:
- break of compilation of openldap if concurrency 1
- break of ffmpeg
Hi all!
Just for those waiting ...
I don't only have no progress, but I am moving backwards.
Last time, I had it to the point where it compiled, but I had issues with nsis.
(See my earlier posting.) Because that nsis issues might be some 64 bit
problem, I set up a new machine with a Debian
: [Ekiga-devel-list] Win32 build broken - status before the
weekend
Quoting Torsten Schlabach [EMAIL PROTECTED]:
Hi all!
Just for those waiting ...
I don't only have no progress, but I am moving backwards.
Last time, I had it to the point where it compiled, but I had
So for anyone wondering what exactly might be wrong ...
I have
Debian lenny (installed yesterday, April 10th)
it's a 32 bit VServer on an AMD64 host machine with a 32 bit userland
Freshly installed packages as per the Wiki page.
I do
# svn co http://svn.gnome.org/svn/ekiga/trunk/win32
Quoting Torsten Schlabach [EMAIL PROTECTED]:
So for anyone wondering what exactly might be wrong ...
I have
Debian lenny (installed yesterday, April 10th)
it's a 32 bit VServer on an AMD64 host machine with a 32 bit userland
Freshly installed packages as per the Wiki page.
I do
# svn
. Unfortunately, I will not be able to continue until
monday.
Regards,
Torsten
Original-Nachricht
Datum: Fri, 11 Apr 2008 14:43:59 +0200
Von: Matthias Schneider [EMAIL PROTECTED]
An: Ekiga development mailing list ekiga-devel-list@gnome.org
Betreff: Re: [Ekiga-devel
Quoting Matthias Schneider [EMAIL PROTECTED]:
Quoting Damien Sandras [EMAIL PROTECTED]:
Le mardi 08 avril 2008 à 17:30 +0200, Torsten Schlabach a écrit :
Damien Sandras wrote:
I only host ekiga.org/ekiga.net and mirror the result of the build done
by Kilian on another machine
PROTECTED]
An: Torsten Schlabach [EMAIL PROTECTED]
CC: ekiga-devel-list@gnome.org
Betreff: Re: [Ekiga-devel-list] win32 build updated
Quoting Torsten Schlabach [EMAIL PROTECTED]:
Good morning!
1. There is still that automake-1.9 versus 1.20 problem. I had to
patch
the Makefile
Le mardi 08 avril 2008 à 10:57 +0200, Matthias Schneider a écrit :
Hm, is it Kilian's? Damien? I can check tonight if it still works...
Hi,
It's Kilian's.
[2.0 build]
What do you mean keep it around? I thought its not working anyway?
I can
only tell you I do not have a single
Le mardi 08 avril 2008 à 16:45 +0200, yannick a écrit :
Le mardi 08 avril 2008 à 10:57 +0200, Matthias Schneider a écrit :
Hm, is it Kilian's? Damien? I can check tonight if it still works...
Hi,
It's Kilian's.
I only host ekiga.org/ekiga.net and mirror the result of the build done
by
Damien Sandras wrote:
I only host ekiga.org/ekiga.net and mirror the result of the build done
by Kilian on another machine (which is not maintained anymore).
What's not maintained anymore? The machine or the build?
Does anyone except Kilian have access to that machine?
Would Kilian grant
Hi all!
Attached please find an interim patch for the win32/Makefile reflecting how far
I got before I will have to call it a day for today.
Please use in conjuction with
http://wiki.ekiga.org/index.php/Cross-compile_Win32
This patch fixes the following:
* automake and friends are
301 - 400 of 414 matches
Mail list logo
