Re: [Ekiga-devel-list] win32 build updated

[Matthias Schneider <matthias schneider TU-Ilmenau DE>]

Quoting Torsten Schlabach <TSchlabach gmx net>:

> Good morning!
>
> > > 1. There is still that automake-1.9 versus 1.20 problem. I had to patch
> > > the Makefile.
> >
> > Yes, but just in 1 place and no longer in 4 places. In case you have an
> > idea how to autodetect this, feel free to contribute.
>
> Not yet, but I am sure, we will find something. Some gnome config script has
> the same problem and they haven't solved that yet AFAIK. It's prio #2 for me,
> right *after* being able to actually run a 3.0 SVN on Windows (see installer
> issue).

Yes, I concur...

> > > - Will we now have a nightly build again?
> >
> > It seems the infrastructure is still up. That means once pptlib and opal
> > build out of the box again, we probably will. If the infrastructure is
> > not up anymore, probably not...
>
> I would be able to donate infrastructure if needed. Who owns the current one?

Hm, is it Kilian's? Damien? I can check tonight if it still works...

> [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 minute I can put into anything
> > related to 2.0.x, actually I had mentally moved the 3.0 windows buidl to
> > 3.2 already...
>
> I mean: Keep the Wiki page where it is and accept a fix to the Makefile if I
> or someone else has one. I am supporting people who use 2.0.11 on Windows
> right now. They have some issues which I might need to fix or which might be
> fixed already in 2.0.12. But I cannot move these people to a moving target
> 3.0 SVN version.
>
> Isn't it good practice to keep bugfixing the stable version of an app until
> the next version is out and usually even running for X amount of time?
>
> I can understand that you cannot / don't want to spent time on it, but others
> might want to. If possible, I'd like to avoid the situation where 2.0 doesn't
> work and 3.0 isn't there yet.

You are right that this should be the way to go. In case you want to contribute
to both 2.x and 3.0 for windows this would be very appreciated. I also did not
know that there are people actually using Ekiga for win since it was never
officially released... However, like I said before I can give you support only
on the 3.0 version.

About 3.0, one known issue is that the DirectShow plugin does not seem to be
linked correctly anymore since the switch to gcc 4.x. Any hint on that would
also be very appreciated (provided ekiga runs at all, which I havent tried for
months...)

> > About the installer, I have no idea right now except that I will compare
> > your nsis version with mine...
>
> Which one do you have? On what distro?

I cannot check before tonight...

> Regards,
> Torsten
Matthias
>
> -------- Original-Nachricht --------
> > Datum: Tue, 08 Apr 2008 08:41:36 +0200
> > Von: Matthias Schneider <matthias schneider TU-Ilmenau DE>
> > An: Ekiga development mailing list <ekiga-devel-list gnome org>, Torsten
> Schlabach <TSchlabach gmx net>
> > CC: Ekiga development mailing list <ekiga-devel-list gnome org>
> > Betreff: Re: [Ekiga-devel-list] win32 build updated
>
> > Quoting Torsten Schlabach <TSchlabach gmx net>:
> >
> > > Hi Matthias!
> > >
> > > Thanks for your effort. I couldn't wait to try it.
> > >
> > > Good news first: It worked 99%! It compiled Ekiga, but it failed to
> > create
> > > the installer. I will attach a complete log file of the entire build.
> > >
> > > Some remarks:
> > >
> > > 1. There is still that automake-1.9 versus 1.20 problem. I had to patch
> > the
> > > Makefile.
> > Yes, but just in 1 place and no longer in 4 places. In case you have an
> > idea how
> > to autodetect this, feel free to contribute.
> >
> > >
> > > 2. It seems to be important to stick to
> > >
> > >   1. make update-sources
> > >   2. apply the patches to OPAL and PTLib (as long as they are needed)
> > >   3. make
> > >
> > > In an earlier attempt, I was curious if I would get the same error
> > message
> > > which you got, so I did not patch, but did a make update-sources, tried
> > a
> > > make, which failed, than patched the libs and tried again, but was
> > unable to
> > > recover.
> >
> > In order to work with the windows buildscript, it is important to know the
> > buildprocess. make update-sources only updates the files in the src
> > directory.
> > Then, when you rebuild, of course you only want to rebuild everything that
> > has
> > changed during that last download, and everything depending on it. This
> > should
> > be working for http downloads, and I have figured a hacked support for SVN
> > as
> > well that does a simple touch on the dir if any file was updated. It does
> > not
> > work for git yet.
> > I.e. if SVN is still at the same revision and no other source file has
> > changed,
> > a new make wont do anything.
> >
> > If you do "make" usually the order is like this:
> > - rm -rf the packages dir
> > - copy if from src to buildroot/libname
> > - patch it
> > - configure it
> > - make it
> > - install it
> > i.e. if you want to rebuild ptlib from a scratch, you can delete the
> > buildroot/ptlib dir and rerun make. if you have changed some file in
> > buildroot/ptlib, you can remove the lib/libpt.a file in order to trigger a
> > rebuild if I remeber correctly. Just have a look on how the dependencies
> > are
> > defined.
> >
> > > Tomorrow I will try and run the .exe on a Windows box and report the
> > results.
> > > I will just have to check how to get it installed without the installer.
> > >
> > > Actually, the dist/Eikiga dir seems to have most of what I would
> > probably
> > > need, but I cannot spot the OPAL and PTLib DLLs there.
> > Its statically linked...
> > >
> > > Additional questions:
> > >
> > > - Will we now have a nightly build again?
> > It seems the infrastructure is still up. That means once pptlib and opal
> > build
> > out of the box again, we probably will. If the infrastructure is not up
> > anymore, probably not...
> > >
> > > > However, we will probably drop the 2.0 stuff
> > > > since it is coming to an end-of-life...
> > >
> > > Can we please keep it around at least until the first release of 3.0 is
> > > available? As long as 3.0 is an entirely moving target, I'd argue that
> > there
> > > are people using 2.0.x in production (either on Linux or Windows) and
> > would
> > > need to be able to fix bugs.
> > What do you mean keep it around? I thought its not working anyway? I can
> > only
> > tell you I do not have a single minute I can put into anything related to
> > 2.0.x, actually I had mentally moved the 3.0 windows buidl to 3.2
> > already...
> >
> > > Obviously, the build which lead to 2.0.11-BETA.exe does not seem to be
> > > reproduceable until know and AFAIK there is no 2.0.12 for Windows at
> > all.
> > >
> > > Regards,
> > > Torsten
> >
> > About the installer, I have no idea right now except that I will compare
> > your
> > nsis version with mine...
> >
> > Matthias
> > >
> > > -------- Original-Nachricht --------
> > > > Datum: Mon, 07 Apr 2008 08:19:16 +0200
> > > > Von: Matthias Schneider <matthias schneider TU-Ilmenau DE>
> > > > An: Ekiga development mailing list <ekiga-devel-list gnome org>
> > > > Betreff: [Ekiga-devel-list] win32 build updated
> > >
> > > >
> > > >
> > > > Hi all,
> > > > due to the huge demand of the win32 build I have updated Ekiga's
> > Makefile
> > > > to
> > > > work with current ptlib, opal and ekiga svn trunk. The only issue
> > > > remaining are
> > > > the changes made in
> > > >
> > > > revision 18828: Fixed UNICODE support issue where wchar_t is not
> > precisely
> > > > the
> > > > same thing as the WORD (aka unsigned short) type previously used in
> > > > strings.
> > > >
> > > > and the corresponding OPAL commit. It completely breaks Ekiga's
> > > > cross-compilation with errors like this:
> > > >
> > > > ./src/ptclib/asner.cxx: In member function 'PBoolean
> > > > PASN_BMPString::IsLegalCharacter(WORD)':
> > > > ./src/ptclib/asner.cxx:1490: error: invalid conversion from 'const
> > short
> > > > unsigned int*' to 'const wchar_t*'
> > > > In file included from ./src/ptclib/asner.cxx:2498:
> > > > ./src/ptclib/asnber.cxx: In member function 'void
> > > > PASN_BMPString::EncodeBER(PBER_Stream&) const':
> > > > ./src/ptclib/asnber.cxx:246: error: invalid cast from type 'const
> > > > PWCharArray'
> > > > to type 'const wchar_t*'
> > > >
> > > > [...]
> > > >
> > > > ./src/ptlib/common/contain.cxx: In constructor 'PString::PString(const
> > > > PWCharArray&)':
> > > > ./src/ptlib/common/contain.cxx:631: error: invalid conversion from
> > 'const
> > > > short
> > > > unsigned int*' to 'const wchar_t*'
> > > > ./src/ptlib/common/contain.cxx:631: error:   initializing argument 1
> > of
> > > > 'void
> > > > PString::InternalFromUCS2(const wchar_t*, int)'
> > > > ./src/ptlib/common/contain.cxx: In member function 'PWCharArray
> > > > PString::AsUCS2() const':
> > > > ./src/ptlib/common/contain.cxx:1695: error: invalid conversion from
> > 'short
> > > > unsigned int*' to 'WCHAR*'
> > > > ./src/ptlib/common/contain.cxx:1695: error:   initializing argument 5
> > of
> > > > 'int
> > > > MultiByteToWideChar(UINT, DWORD, const CHAR*, int, WCHAR*, int)'
> > > >
> > > > Craig, Robert, I do not know if you are both subscribed to this list,
> > but
> > > > if you
> > > > are, could you give it a look?
> > > >
> > > > In case someone wants to build a win32 ekiga he/she can do the
> > following:
> > > > - get the buildscript like described on the wiki
> > > > - make update-sources
> > > > - aplly the enclosed patches to opal and ptlib, which revert the
> > WideChar
> > > > commits
> > > > - make
> > > >
> > > > The resulting executable and installer have not been tested by me
> > though,
> > > > so no
> > > > guarantee it will work...
> > > >
> > > > I have also updated the wiki, separating 2.0 stuff from 3.0 stuff.
> > > > However, we
> > > > will probably drop the 2.0 stuff since it is coming to an
> > end-of-life...
> > > >
> > > > Matthias
> > > >
> > > >
> > > >
> > > > ----------------------------------------------------------------
> > > > This message was sent using IMP, the Internet Messaging Program.
> > > _______________________________________________
> > > Ekiga-devel-list mailing list
> > > Ekiga-devel-list gnome org
> > > http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
> > >
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
>




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.