gmane.network.jabber.psi.devel

Re: l10n server went down

Justin Karneges — 2012-05-17T18:29:19

Thanks Frederik. We'll look at restoring this.

On Thursday, May 17, 2012 10:09:40 AM Frederik Schwarzer wrote:

l10n server went down

Frederik Schwarzer — 2012-05-17T17:09:40

Hi,

for the last three years I ran the l10n server for Psi with automatic 
string extraction and Git archives for each language. That server is 
no longer available because I am not at the institute anymore that 
hosted it.

Since I do not have another server and also not the time to set 
everything up again, the l10n server is down and will remain so for 
now.

I provide the Git archives at
http://fs.scs-tsa.de/public/
for download as zip archives.

Download "all-psi-l10n.zip" if you want all archives or, if you are 
only interested in a single language, the respective "psi-l10n-
xx.git.zip".

If you have any questions, feel free to ask.

Regards

Re: How to build psi in Qt Creator?

Rion — 2012-04-28T15:23:13

disable shadow build in qt creator settings. its unsupported for Psi.
btw 0.15 will be released soon. why are you building 0.14?

2012/4/28  <ondrejandrej-9Vj9tDbzfuSlVyrhU4qvOw< at >public.gmane.org>:

Re: How to build psi in Qt Creator?

2012-04-28T15:17:04

I didn't want to bother everybody in the mailing list with a large file, so you can view the whole build log under this link:

http://physics.muni.cz/~repisky/psi_build_log_qt_creator.txt

Andrej

Re: How to build psi in Qt Creator?

Rion — 2012-04-27T02:19:39

can you show whole build log or at least begining from linking?

2012/4/27  <ondrejandrej< at >seznam.cz>:
_______________________________________________
Psi-Devel mailing list
Psi-Devel< at >lists.affinix.com
http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com

Re: How to build psi in Qt Creator?

2012-04-26T21:18:46

Thanks. I get a different kind of error now :-)

/usr/bin/ld: cannot find -lqca_psi
/usr/bin/ld: cannot find -liris

These lines appear after the final build step (g++ call which should link all .o files into executable). However, both libqca_psi.a and libiris.a are present in the directories specified by g++ -L option. I tried to run make --debug on psi sources extracted to a different directory and everything seems to work fine. So I tried to replace the two files with the files produced by make (they have different sizes), but the error remains.

Any ideas?

Andrej


_______________________________________________
Psi-Devel mailing list
Psi-Devel< at >lists.affinix.com
http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com

Re: How to build psi in Qt Creator?

Rion — 2012-04-26T14:27:51

You have to call configure script (probably with --debug option) and
then open in qt creator.


2012/4/26  <ondrejandrej-9Vj9tDbzfuSlVyrhU4qvOw< at >public.gmane.org>:

How to build psi in Qt Creator?

2012-04-26T13:20:15

Hi,

I'd like to modify Psi for my own purpose and I prefer to use Qt Creator. I opened psi.pro and clicked Rebuild all, but after a while the compiler complains PSI_LIBDIR is not declared in applicationinfo.cpp. I get lots of warnings as well.

What do you guys use as an IDE for development? If it's Qt Creator, how can I get it working?

Thanks, 

Andrej

psideps

Justin Karneges — 2012-04-06T07:37:06

To help deal with Psi dependencies on non-Linux platforms, I've created a new 
repository called "psideps". In here will be a collection of scripts and such, 
for automatically downloading and compiling dependency packages from source, 
and doing whatever is necessary to get the results in a releasable state 
(cross-compiling, install_name_tool'ing, etc). It's halfway to Gentoo!

The scripts are a good mix of simplicity and robustness. There's no real magic 
going on, but if something breaks during a build you can easily get in there 
and repair things.

On Windows this will require an MSYS environment.

Official binaries will be placed in http://psi-im.org/files/deps/ so most people 
building Psi can just grab those files without ever having to build anything 
through psideps. The psideps repo is mostly useful for me, as a replacement 
for my legacy non-automated, undocumented, arcane processes used to build 
dependencies that I've used in the past.

Currently there are scripts to build gstreamer on Mac, and I've uploaded a 
binary package. It works enough to run gst-launch. I have not tried to compile 
PsiMedia against it yet.

Next will be to do other dependencies like Growl, OpenSSL, etc.

Justin

Re: gstreamer

Justin Karneges — 2012-04-05T21:04:27

I've tested on a bunch of platforms (Windows 7/XP, Mac Snow Leapard, Ubuntu 
11.04). There is an audio synchronization bug in 0.10.36 (the latest stable), 
however it is not present in 0.10.35 and it is already fixed for the next 
release (0.10.37 and/or 0.11/1.0).

Audio output works fine on all platforms. I only tested audio input on Mac, due 
to lack of a microphone on my Windows and Linux systems. I'd be shocked if 
audio input didn't work on those platforms though, given the code overlap with 
audio output, but I'll try to confirm soon just to be sure. Also, once I 
produce binaries it should be easy for others to test this stuff too.

Video on Mac and Linux seems to work well. I'm going to drop support for v4l1 
in PsiMedia. Psi doesn't officially support video calling yet anyway so I don't 
feel the need to continue maintaining support for ancient devices. If you're 
on Linux, do me a favor and confirm your camera is v4l2. Video on Windows is a 
crapshoot. Initializing the camera worked every other try for me. The 
ksvideosrc element has always felt unstable so I consider this situation not 
worse than it already was.

Current PsiMedia depends on gstreamer/gst-plugins-base 0.10.22 or higher. I'm 
going to bump this number up so I can get rid of some bundled code that is now 
present and stable in GStreamer itself.

Therefore, PsiMedia shall target gstreamer/gst-plugins-base 0.10.24 or higher, 
with corresponding gst-plugins-good 0.10.16 or higher, both released August 
2009. However, gst-plugins-base 0.10.36 should be avoided as it contains known 
issues.

Windows/Mac binaries produced for Psi will use the latest stable version 
(gstreamer/gst-plugins-base 0.10.36 and gst-plugins-good 0.10.31), but with 
known issues patched.

For the Psi 0.15 schedule, there is no plan to merge code into GStreamer or 
otherwise perform GStreamer development. We'll simply use the above versions 
mentioned, with patching in the case of binaries.

LONG TERM:

GStreamer has two active branches right now: 0.11 (current development, to be 
crowned 1.0 this year) and 0.10 (current stable). We catch the project at kind 
of a bad moment, since it is unlikely they will accept major changes to the 
0.10 branch. Therefore all pending merges from PsiMedia will be reworked 
against 0.11 / 1.0. PsiMedia will likely not target 0.11/1.0 for quite some 
time though, so this is very forward-looking stuff and not part of the Psi 0.15 
schedule.

Justin

Re: State of XEP-0198 support

Tobias Markmann — 2012-04-05T10:44:49

Here the two repos (Iris and Psi) changes:

Iris: https://github.com/tfar/iris-gsoc2010

Psi: https://github.com/tfar/psi-soc2010

Cheers,
Tobi

Re: State of XEP-0198 support

Georg Lukas — 2012-04-05T06:41:15

* Rion <rion4ik-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> [2012-04-05 06:07]:

Is there a place I can find the unmerged source code? I am interested in
the SM protocol version it supports :)


Kind regards,

Georg

Re: State of XEP-0198 support

Rion — 2012-04-05T04:04:15

2012/4/5 Tobias Markmann <tmarkmann-gM/Ye1E23mwN+BqQ9rBEUg< at >public.gmane.org>:
it certainly will be merged. but not sure for which version.

gstreamer

Justin Karneges — 2012-04-04T20:25:09

I'm working on getting up to speed with the latest GStreamer. A lot changes in 
two years:

 - GStreamer has had 14 new releases
 - GStreamer is preparing a major version update with API/ABI breakage
 - liboil is gone
 - v4l1 support was dropped from the kernel. i have no v4lsrc element on my 
Ubuntu 11.04 computer.
 - new codecs like VP8, opus

GStreamer is a complex project that is highly susceptible to regressions. Even 
the latest stable (0.10.36) adds bugs that we didn't have in 0.10.22 from back 
in 2009.

I'm building/testing GStreamer on all platforms, and working with the 
developers to fix any bugs I come across that would affect us. My goal is for 
the voice calling feature of Psi 0.15 to work just as well as it did in 0.14, 
against a relatively modern version of GStreamer. I have not yet determined 
what that version should be, but hopefully won't be 0.10.37.

Justin

Re: State of XEP-0198 support

Tobias Markmann — 2012-04-04T19:57:47

If someone has time and will-power to merge this back in, I'm happy to
help with this.

Cheers,
Tobi

Re: State of XEP-0198 support

Justin Karneges — 2012-04-04T19:52:22

Unfortunately it was never merged in, so the simple answer is that Psi does 
not support XEP-0198 yet.

Justin

State of XEP-0198 support

Georg Lukas — 2012-04-04T18:39:23

Hello,

I am on a quest to document the state of XEP-0198 (Stream Management [1])
implementation in different XMPP applications [2], as a part of my
compatibility research for yaxim, Yet Another XMPP IM client for
Android [3].

I found some hints that the XEP was implemented in Psi during a 2010
GSoC. However, I was not able to find any traces of the XEP in Psi's
source code from git.

Does Psi implement XEP-0198 in the main development branch or some other
branch / repository?

If yes, which version of the XEP (the X in "urn:xmpp:sm:X") is
implemented?

I would be very grateful to receive the information or some pointers
into the right direction.


Kind regards,


Georg

[1] http://xmpp.org/extensions/xep-0198.html
[2] http://op-co.de/blog/posts/XEP-0198/
[3] http://yaxim.org/

Re: drop osx tiger?

James Bunton — 2012-04-04T09:08:19

I wonder if recent Qt versions even support 10.4 anymore.

If anybody wants to try, I have a copy of the older SDKs:
http://delx.net.au/files/others/MacOSX10.4u.sdk.zip
http://delx.net.au/files/others/MacOSX10.5.sdk.zip

--

James

Re: 0.15 Beta1

Remko Tronçon — 2012-04-03T07:12:56

I had to throw away the current implementation, and rewrite it in
Objective-C++. But all in all, it wasn't that much work i seem to
recall.

cheers,
Remko

Re: drop osx tiger?

Kevin Smith — 2012-04-03T07:06:20

I wouldn't bother.

/K

Re: drop osx tiger?

Dmitry Nezhevenko — 2012-04-03T07:03:16

Which version of Xcode you've? 10.4 is probably 3.2.x only and not
installed by default (there is separate checkbox for it IIRC).

PS. Also if you're building Qt yourself, make sure that you're using
something NOT named llvm-gcc (gcc --version should not output that it's
llvm-gcc). It's apple-only crap that has so many bugs that it's much
easier to ignore it at all than to fix/workaround all of them.