[Psi-Devel] 0.15 Beta1
Justin Karneges
To kick off the 0.15 release process I've made some beta packages:
https://sf.net/projects/psi/files/Development%20Snapshots/0.15-beta1/
Source and Windows (32-bit) are there now. Mac will follow shortly.
Please note that this is a BETA and not a release candidate. I've merely
packaged the master branch, which is still under development.
This version contains about two years worth of merges from the Psi+ project.
Thanks to Rion and Dealer_WeARE for diligently keeping the Psi source repo
current all this time.
The next step will be to discuss what should be done for 0.15 final and set a
schedule.
Justin
_______________________________________________
Psi-Devel mailing list
Psi-...@lists.affinix.com
http://lists.affinix.com/listinfo.cgi/psi-devel-affinix.com
Justin Karneges
> Source and Windows (32-bit) are there now. Mac will follow shortly.
And now a Mac build is available, too. This one is 64-bit only, and lacks
Growl support and voice calling.
It's not immediately clear to me how to target multiple architectures using Qt
4.8.1 on a 64-bit host. At least, Psi's usual build directives for 32-bit
x86/ppc don't seem to be working. Maybe someone knows?
The PsiMedia binaries are 32-bit only, which makes them incompatible with a
64-bit build. This is why voice calling is missing.
Growl is missing because I don't quite understand their licensing situation.
It seems they've gone payware, but there is a free option called "Mist". Maybe
there is no problem here, and I just need to take a closer look.
Kevin Smith
> 2012/4/1 Remko Tronçon <re...@el-tramo.be>:
>> On Sun, Apr 1, 2012 at 10:30 AM, Kevin Smith <ke...@kismith.co.uk> wrote:
>>> /Users/kismith/src/qt-everywhere-opensource-src-4.8.1/configure
>>> -arch x86 -no-qt3support -sdk /Developer/SDKs/MacOSX10.6.sdk -cocoa
>>> -opensource --confirm-license
>>
>> And the QMAKE part (both axises of architecture):
>> CONFIG += x86 ppc x86_64 ppc64
>>
>> I would just stick with x86 and ppc personally, unless you want to put
>> yourself through the pain and bandwidth of supporting 64 bit in all
>> your dependent libraries.
>
> Though if you want to cover PPC as well you'll need to cover the 10.5 SDK.
*target the 10.5 SDK...
Justin Karneges
> On Sun, Apr 1, 2012 at 10:30 AM, Kevin Smith <ke...@kismith.co.uk> wrote:
> > /Users/kismith/src/qt-everywhere-opensource-src-4.8.1/configure
> > -arch x86 -no-qt3support -sdk /Developer/SDKs/MacOSX10.6.sdk -cocoa
> > -opensource --confirm-license
>
> And the QMAKE part (both axises of architecture):
> CONFIG += x86 ppc x86_64 ppc64
>
> I would just stick with x86 and ppc personally, unless you want to put
> yourself through the pain and bandwidth of supporting 64 bit in all
> your dependent libraries.
Ah, I clearly can't read. The binaries on qt.nokia.com are 64-bit only:
http://qt.nokia.com/downloads/qt-for-open-source-cpp-development-on-mac-os-x
$ file /Library/Frameworks/QtCore.framework/QtCore
/Library/Frameworks/QtCore.framework/QtCore: Mach-O 64-bit dynamically linked
shared library x86_64
Building from source now to get multi-arch.
Justin Karneges
> On Sun, Apr 1, 2012 at 9:20 AM, Justin Karneges <jus...@affinix.com> wrote:
> > Growl is missing because I don't quite understand their licensing
> > situation. It seems they've gone payware, but there is a free option
> > called "Mist". Maybe there is no problem here, and I just need to take a
> > closer look.
>
> provide prebuilts through the store.
Alright, I built the Growl 1.2.2 framework from source, and will include this
in the next beta build.
Kevin Smith
> On Sunday, April 01, 2012 01:30:03 AM Kevin Smith wrote:
>> On Sun, Apr 1, 2012 at 9:20 AM, Justin Karneges <jus...@affinix.com> wrote:
>> > Growl is missing because I don't quite understand their licensing
>> > situation. It seems they've gone payware, but there is a free option
>> > called "Mist". Maybe there is no problem here, and I just need to take a
>> > closer look.
>>
>> Source is still free, you can grab and compile yourself. They also
>> provide prebuilts through the store.
>
> Alright, I built the Growl 1.2.2 framework from source, and will include this
> in the next beta build.
I think you need to use the 1.3 one if you also want it to work with
modern Growls.
/K
Remko Tronçon
> know if the API changes were simple?
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