Maybe another possibility is to hang in a second mac slave to built
maclauncher/FlightGear against SDK 10.5 and target 10.5. I could spend one of
my FGx slaves once for such, when it makes sense for the project to get 10.5
support on intel back. Or another possibility is I try to build the offic
Hi Curt
I would not recommend to get 10.5 support back with current official jenkins
build. AFAIK current mac build for 10.6/7/8 works very well, supporting 10.5
would need heavy changes, or better, downgrading of slaves, and it is
definitely not worth to break things this way. I'm free to do s
On 18 Feb 2013, at 17:08, Curtis Olson wrote:
> I haven't been following this thread too closely, but is it possible to get
> 10.5 support back into the official build on Jenkins or does it require a
> separate build/installer for 10.5 support?
>
I think the answer is no, since the build sla
On Mon, Feb 18, 2013 at 11:00 AM, ys wrote:
> O, happy now.
>
> Finally it is working. And 2.10 is really a hit, compiled against sdk
> 10.5. One can still use an older macbook for simple multi-machine fun, with
> an old osx with bad bad graphics (old ATI, almost no vram). Now turning on
> 3d
O, happy now.
Finally it is working. And 2.10 is really a hit, compiled against sdk 10.5. One
can still use an older macbook for simple multi-machine fun, with an old osx
with bad bad graphics (old ATI, almost no vram). Now turning on 3d clouds,
water, crop and transistion shader ... everyt
Hi James
Have some news, I got sound back with simgear/sound/openal_tests, compiled
against sdk 10.6. Now I'm going to make some other tests with fg vs. 10.5. What
I changed in my chain is nuking macports boost 1.52 and bringing back 1.50 with
a manual install on the slave.
I've seen that your
Am 16.02.2013 um 00:56 schrieb ys :
> so I really have no idea what might be going.
Hi James
Me too. But it is still here. SimGear throws the same issue with all
combinations I tried, and now after goinf for 2.10 also with SDK 10.6. Meantime
I guess it is more a general problem, I don't k
Am 16.02.13 18:54, schrieb HB-GRAL:
> I got also the sound working now for 10.5, and I'm actually building a
> FGx 2.10 against SDK 10.5.
The sound problem is not related to 10.5 of course, I got the sound
working for arch i386 and sdk 10.5/6 (x86_64 worked from beginning,
building against sdk 1
Hi James
I'm still trying to be this 10.5 person these days, I don't give up that
fast of course ;-) And I spent a lot of time this week in this believe me.
It started with having all dependencies right, and now I'm still trying
to get simgear/flightgear the right way. When I succeed I will nee
On 15 Feb 2013, at 23:56, ys wrote:
> Ok, can we have a decision that SimGear/FlightGear is not supporting OSX 10.5
> on intel anymore ? FG 2.8 is doable, and maybe 2.10 with some further tweaks
> too, but after looking to what's coming up with "next" I see that more and
> more tweaks are nee
Hi all
Ok, can we have a decision that SimGear/FlightGear is not supporting OSX 10.5
on intel anymore ? FG 2.8 is doable, and maybe 2.10 with some further tweaks
too, but after looking to what's coming up with "next" I see that more and more
tweaks are needed and that core developers do not tak
On Wed, 13 Feb 2013 10:39:45 +, James wrote in message
<403c7d2a-377f-4f69-951d-7d574ba84...@mac.com>:
>
> On 13 Feb 2013, at 10:05, ys wrote:
>
> > Are you using a flag on jenkins shell or rb script I couldn't see
> > and I need to take into account? should I try on another machine
> > fi
Hi James
Thanks a lot for all your replies, gave me some hope ;-) But I guess I'm not
able to make FGx possible for mac users with built-in osg/sg/fg the next days,
because of this strange sound problem. Ok, this doesn't matter that much,
because FGx is only a very small side project and an uno
On 13 Feb 2013, at 10:05, ys wrote:
> Are you using a flag on jenkins shell or rb script I couldn't see and I need
> to take into account? should I try on another machine first ... Or is there
> some mystic endianess I should take into account for this first generation
> intel macs? I wonder
Hi James
I'm stuck with this now. And no, there is no arch PPC, I'm just compiling with
i386 against SDK 10.5 and target 10.5 with arch i386 only, but also when I
switch to 10.6 SDK and target 10.6 I get no wav sound and fg hangs. I opened
the wavs with other software, no problem, I downloaded
On Feb 11, 2013, at 03:05 PM, ys wrote:Hi James I guess this forking would be possible with the cocoa and the svn patch, but I'm struggling with something different at the moment. Everything compiles fine against 10.5 but when I start flightgear I have no engine sound, and when engine sounds are
Hi James
I guess this forking would be possible with the cocoa and the svn patch, but
I'm struggling with something different at the moment. Everything compiles fine
against 10.5 but when I start flightgear I have no engine sound, and when
engine sounds are activated fg hangs (no segfault). I c
On 10 Feb 2013, at 13:48, ys wrote:
> So my goal is to have flightgear 2.10 still up for using on a second old
> intel machine in the network (no ppc, but where 10.5 install was the origin
> and therefor probably the fastest, 10.7 does not run on this machines and
> 10.6 is not a free update)
Hi James
Sounds like paranoia on my side, about a "decision", sorry for that. But I
feared that I missed some discussion about 10.5 and spend too much time on
something that isn't a goal anymore ..
So my goal is to have flightgear 2.10 still up for using on a second old intel
machine in the ne
On 9 Feb 2013, at 20:49, ys wrote:
> But with some small directives I tested today I see that it would be possible
> to still port fg 2.8 and 2.10 for osx sdk 10.5. I don't want to offend anyone
> for this >= 10.6 decision or the code, but please can you point me to some
> sources posts/threa
Hi all
While there is absolutely no problem to compile OSG and other deps against osx
sdk 10.5 there has been some bits introduced in simgear/flightgear now to not
compile against sdk 10.5 anymore. The cocoa code I already mentioned requires
only a small directive (sorry about the dyslexia in m
21 matches
Mail list logo
