Re: [Flightgear-devel] OSX 10.5 compilation
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 official maclauncher out of jenkins locally here with such a setting, and when it is working you can put that to a separate 10.5 download. I would offer this work when there is some request for this, but first ... I would try to get atlas support back for osx when possible. I'm not able to compile atlas and I guess this is a really hard one for all osx versions. I hope that my findings with this can help the official launcher. It was always included with former version when I'm not wrong, and FGx doesn't support atlas either these days, unfortunately. (Another minority probably, but for me personally atlas is still one of the best maps we have, even this is a very old and a bit outdated project). -Yves Am 19.02.2013 um 02:07 schrieb ys flightg...@sablonier.ch: 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 such on a small private CI, and I made a lot of noise about having 10.5 support back, but at the end it's just weird and for a very small minority of fg users like me. But it is documented, and everyone joining the adventure can do so ;-) -Yves Am 18.02.2013 um 18:54 schrieb James Turner zakal...@mac.com: On 18 Feb 2013, at 17:08, Curtis Olson curtol...@flightgear.org 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 slave runs 10.6. If someone else disagrees, then I need to proceed carefully, since rebuilding the slave if we screw something up is not fun. (I could image the drive, I guess) James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 jenkins slave uses 1.52. Maybe this works well with devtools = 4, here I'm using 3.2.6 for the slave to get sdk 10.5. Is there a reason to install boost 1.52, or is 1.50 ok for the next days ? ;-) And another question, do you remember what options you used for installing boost 1.52 on the slave ? Thanks, Yves Am 18.02.2013 um 03:01 schrieb ys flightg...@sablonier.ch: Am 16.02.2013 um 00:56 schrieb ys flightg...@sablonier.ch: 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 know what the wavreader throws when the path is wrong to the wav file i.e. Because in the error message I don't see any path, and when I'm looking to the wavreader code it should throw the path, or not ? So next question is does the wavreader throw truncated or corrupt when it doesn't find the .wav file ? I edited the simgear code and realised that what I see in fg log is the first exception that can be thrown with message truncate/corrupt. Any other ideas what I should take into account ? -Yves -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 ... everything looks fine with a reasonable framerate (around 20fps). Only atmospheric lights, urban shader, random buildings/vegetation and some AI traffic reduces framerate to a no go. But really, well done, thanks guys. And special thanks to James and others nuking alut and making building sg/fg on a mac easier and easier (beside of my sound and boost troubles the last days, but that's just a private 2.10/osx learning curve here, I see). I am happy for the rest of the week (and shut up) because I got 2.10 working now from OSX 10.5 to 8, with simply downgrading boost and nuking macports. I will publish a version with FGx asap. Now I see that the small cocoa change for flightgear making compiling possible for 10.5 has already been merged by James, thanks, the patch for the simgear sdk 10.5 svn problem will follow asap. Thanks, Yves Am 18.02.2013 um 14:41 schrieb ys flightg...@sablonier.ch: 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 jenkins slave uses 1.52. Maybe this works well with devtools = 4, here I'm using 3.2.6 for the slave to get sdk 10.5. Is there a reason to install boost 1.52, or is 1.50 ok for the next days ? ;-) And another question, do you remember what options you used for installing boost 1.52 on the slave ? Thanks, Yves Am 18.02.2013 um 03:01 schrieb ys flightg...@sablonier.ch: Am 16.02.2013 um 00:56 schrieb ys flightg...@sablonier.ch: 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 know what the wavreader throws when the path is wrong to the wav file i.e. Because in the error message I don't see any path, and when I'm looking to the wavreader code it should throw the path, or not ? So next question is does the wavreader throw truncated or corrupt when it doesn't find the .wav file ? I edited the simgear code and realised that what I see in fg log is the first exception that can be thrown with message truncate/corrupt. Any other ideas what I should take into account ? -Yves -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 clouds, water, crop and transistion shader ... everything looks fine with a reasonable framerate (around 20fps). Only atmospheric lights, urban shader, random buildings/vegetation and some AI traffic reduces framerate to a no go. But really, well done, thanks guys. And special thanks to James and others nuking alut and making building sg/fg on a mac easier and easier (beside of my sound and boost troubles the last days, but that's just a private 2.10/osx learning curve here, I see). I am happy for the rest of the week (and shut up) because I got 2.10 working now from OSX 10.5 to 8, with simply downgrading boost and nuking macports. I will publish a version with FGx asap. Now I see that the small cocoa change for flightgear making compiling possible for 10.5 has already been merged by James, thanks, the patch for the simgear sdk 10.5 svn problem will follow asap. 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? Thanks, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On 18 Feb 2013, at 17:08, Curtis Olson curtol...@flightgear.org 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 slave runs 10.6. If someone else disagrees, then I need to proceed carefully, since rebuilding the slave if we screw something up is not fun. (I could image the drive, I guess) James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 such on a small private CI, and I made a lot of noise about having 10.5 support back, but at the end it's just weird and for a very small minority of fg users like me. But it is documented, and everyone joining the adventure can do so ;-) -Yves Am 18.02.2013 um 18:54 schrieb James Turner zakal...@mac.com: On 18 Feb 2013, at 17:08, Curtis Olson curtol...@flightgear.org 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 slave runs 10.6. If someone else disagrees, then I need to proceed carefully, since rebuilding the slave if we screw something up is not fun. (I could image the drive, I guess) James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
Am 16.02.2013 um 00:56 schrieb ys flightg...@sablonier.ch: 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 know what the wavreader throws when the path is wrong to the wav file i.e. Because in the error message I don't see any path, and when I'm looking to the wavreader code it should throw the path, or not ? So next question is does the wavreader throw truncated or corrupt when it doesn't find the .wav file ? I edited the simgear code and realised that what I see in fg log is the first exception that can be thrown with message truncate/corrupt. Any other ideas what I should take into account ? -Yves -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On 15 Feb 2013, at 23:56, ys flightg...@sablonier.ch 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 needed and that core developers do not take 10.5 into account anymore (what I can understand very well, but it's not mentioned anywhere, when I'm not wrong). Fact is that all dependencies still supports osx 10.5 on intel, but sg/fg doesn't anymore (since 2.8 this is also posted at flightgear.org for mac release, = 10.6). As stated by James sg/fg code is not tested against 10.5 by core developers anymore, so please ... I my view a small message should come to changelog which can be referenced by supporters at forums and elsewhere for this fact. Or do you think this is completely wrong ? Hmm, I'm not sure what to say - I'm not aware of any 'upcoming' stuff in next that makes 10.5 support harder. There's changes, e.g. the file-dialog stuff, if it does't work with 10.5 (and I've no idea if does or not), can simply be #ifdef-ed based on the system version. That's the *only* think I can think of in next which would affect system support. And I maintain, that 10.5 support is pretty doable with the 2.10 codebase, or 'next', if someone wishes to invest some time. So making an 'official statement' seems a bit silly - just like it would be odd to make a statement saying we don't support FreeBSD or Cygwin or Windows 2k. I imagine some of those platforms need a similar amount of tweaking to Mac 10.5, to work out of the box, since no one tried them in years, but if someone cares to make them work, they will work - and I'm happy to apply patches to support them, so long as they don't break existing stuff. (Actually I think FreeBSD does work, precisely because someone did that work, for 2.8) So we can make such a statement, and if someone asks, the reason for making the statement, is because you asked for such a statement! - but I don't really see who that benefits? It will still be possible to #ifdef some code and support 10.5, if there's a person interested / motivated enough to make it happen. Regards, James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 need some tests (by real 10.5 users, but also by users up to 6/7/8). I will clone the sg/fg repositories and add the directives, send some merge requests. Actually there are only two small changes in code checked in by you: The cocoa clipboard code in flightgear source (the patch I already sent), and in simgear svn_cmdline_create_auth_baton and svn_client_checkout3 which can't be used with sdk 10.5. But the alternatives here are already in place, it just needs a clever directive using the SVN_VER_MINOR already there. I got also the sound working now for 10.5, and I'm actually building a FGx 2.10 against SDK 10.5. When I succeed I will post a download link at forums to test, and then I will bring the small changes I made to a clone/merge request to verify. Thanks, Yves Am 16.02.13 15:15, schrieb James Turner: On 15 Feb 2013, at 23:56, ys flightg...@sablonier.ch 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 needed and that core developers do not take 10.5 into account anymore (what I can understand very well, but it's not mentioned anywhere, when I'm not wrong). Fact is that all dependencies still supports osx 10.5 on intel, but sg/fg doesn't anymore (since 2.8 this is also posted at flightgear.org for mac release, = 10.6). As stated by James sg/fg code is not tested against 10.5 by core developers anymore, so please ... I my view a small message should come to changelog which can be referenced by supporters at forums and elsewhere for this fact. Or do you think this is completely wrong ? Hmm, I'm not sure what to say - I'm not aware of any 'upcoming' stuff in next that makes 10.5 support harder. There's changes, e.g. the file-dialog stuff, if it does't work with 10.5 (and I've no idea if does or not), can simply be #ifdef-ed based on the system version. That's the *only* think I can think of in next which would affect system support. And I maintain, that 10.5 support is pretty doable with the 2.10 codebase, or 'next', if someone wishes to invest some time. So making an 'official statement' seems a bit silly - just like it would be odd to make a statement saying we don't support FreeBSD or Cygwin or Windows 2k. I imagine some of those platforms need a similar amount of tweaking to Mac 10.5, to work out of the box, since no one tried them in years, but if someone cares to make them work, they will work - and I'm happy to apply patches to support them, so long as they don't break existing stuff. (Actually I think FreeBSD does work, precisely because someone did that work, for 2.8) So we can make such a statement, and if someone asks, the reason for making the statement, is because you asked for such a statement! - but I don't really see who that benefits? It will still be possible to #ifdef some code and support 10.5, if there's a person interested / motivated enough to make it happen. Regards, James -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 10.6). There are four possibilities that made it running finally now, independent of the machine, I don't know which one (or all of this?) I should take into account for my build, I will check all of this again: 1) building against OSG 3.1.3 instead of trunk (3.1.5) 2) rebuilding plib and not using macports plib (at least for 10.5 this is necessary anyway because I can't use 10.6 macports plib of course) 3) enable fgpanel and getting glut with this (huh?) 4) building with RTI=off But I'm only talking to myself here, sorry for that. I promise I will get more overview soon and shut up. -Yves -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 take 10.5 into account anymore (what I can understand very well, but it's not mentioned anywhere, when I'm not wrong). Fact is that all dependencies still supports osx 10.5 on intel, but sg/fg doesn't anymore (since 2.8 this is also posted at flightgear.org for mac release, = 10.6). As stated by James sg/fg code is not tested against 10.5 by core developers anymore, so please ... I my view a small message should come to changelog which can be referenced by supporters at forums and elsewhere for this fact. Or do you think this is completely wrong ? -Yves Am 13.02.2013 um 22:19 schrieb ys flightg...@sablonier.ch: 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 unofficial fg side release, even when I tried to follow the official release plan with this piece the last months. Maybe it's a simple slave hardware issue, or there is some strange behaviour with the macports setup and I need to hang another machine with a fresh new install into jenkins. As the official mac release has working sound I guess it's really not related to sg/fg code at all, sorry for the noise. And as a launcher without built-in libs FGx still works on macs, also with 2.10. All these things need a lot of time, and many thanks for your support and thoughts. When I installed a jenkins some months ago I thought we can switch version with the new build, skipping a dependency here and there, and build it, release, finish, without a lot of tweaks. Forget that with flightgear (and Yves, and osx, and all this old unused machines) ;-) My last hope is now that I can bring back some findings that are useful for others the next days probably, and that I get a new build that makes FGx 2.10 also possible for mac users. It's not impossible, but I still have no idea why the sound has gone. -Yves Am 13.02.2013 um 11:39 schrieb James Turner zakal...@mac.com: On 13 Feb 2013, at 10:05, ys flightg...@sablonier.ch 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 that I had absolutely no problems with alut and 2.8 some months ago. If you're on Intel, and the 2.10 official release works, I am stumped. The code is /extremely/ simple - open file, read some bytes. There's no scripts or options or anything to control it, as far as I know. And there's no mystic endian-ness, and plenty of people on Linux use 32-bit builds - so I really have no idea what might be going. Sorry, not helpful I realise. James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 flightg...@sablonier.ch 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 that I had absolutely no problems with alut and 2.8 some months ago. If you're on Intel, and the 2.10 official release works, I am stumped. The code is /extremely/ simple - open file, read some bytes. There's no scripts or options or anything to control it, as far as I know. And there's no mystic endian-ness, and plenty of people on Linux use 32-bit builds - so I really have no idea what might be going. Sorry, not helpful I realise. ..does it work in any of FreeBSD, NetBSD or OpenBSD? Those are the closest relatives to Apple's Mac OS X: http://en.wikipedia.org/wiki/OS_X http://en.wikipedia.org/wiki/History_of_OS_X http://en.wikipedia.org/wiki/OpenStep http://en.wikipedia.org/wiki/GNUstep ..finally, the problem _may_ be Apple policy, e.g. endlifing OS x 10.5 or expansion of iTunes style restrictions on unapproved apps, where e.g. FlightGear is NIH, after all, Steve Jobs wanted nuclear war on Android: http://www.google.com/search?q=%22Steve+Jobs%22+%22nuclear+war%22+android http://en.wikipedia.org/wiki/Mobile_operating_system#Market_share http://en.wikipedia.org/wiki/Not_invented_here http://en.wikipedia.org/wiki/Apple_Inc._litigation#Norwegian_Consumer_Council http://en.wikipedia.org/wiki/Apple_Inc._litigation#Apple_v._Samsung:_Android_phones_and_tablets http://www.groklaw.net/staticpages/index.php?page=AppleSamsung http://www.groklaw.net/staticpages/index.php?page=AppleSamsung http://www.groklaw.net/staticpages/index.php?page=20120817052356762 -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 2.10 release dmg and run it with 10.6 on this machine ... and get no sound problems?! I checked CMakeCache of simgear and flightgear on jenkins against my cache and could not find any important difference. The only thing different is that I use arch i386 explicitely and I set SDK and target with cmake. The log shows the same, sound is enabled ... I checked all the links of fgfs, exactly the same. I'm assuming that simpits mac is i386 too and is the same hardware generation more or less (but I'm not sure about). 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 that I had absolutely no problems with alut and 2.8 some months ago. I could try to compile on another slave, a x86_64 machine and have a look what happens there, or I could edit the wavreader code to see more clearly where the problem occurs and if it's really the byte order (what I could not imagine, but one never knows). No other ideas at the moment. Arghh, maybe it's just a small little thiny bit I miss, a new simgear/flightgear build guru bity I don't get. Thanks, Yves Am 12.02.2013 um 15:23 schrieb James Turner zakal...@mac.com: On Feb 11, 2013, at 03:05 PM, ys flightg...@sablonier.ch 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 activated fg hangs (no segfault). I can only startup with aircrafts that have no engines running (i.e. c172p or b1900), the others will crash flightgear and I get a simgear log entry that the associated wav files are corrupted or truncated. Ehrm, looking where this message is generated there are a lot of possibilities in your new wavreader ;-) Can you give me any hint where this OpenAL sound problem could reside? Strange thing is that avionics sound works (i get some 'instrument beeps' in b1900 i.e.), only the engine is a problem. When I turn off sounds (switching off master in the GUI) everything works as expected, I get 30 fps without shaders and out of KSFO, keys are working etc. Maybe this is not related to 10.5 at all and there are some other important changes/patches for osx compilation I missed after alut nuke ? To be honest I have no ideas - the WAV reading code is extremely simple, and copied directly from the ALUT sources - it's used everywhere - Windows, Linux and Mac, with no #ifdefs. So I can't imagine why some sounds would work and not others. Except, some of our beeps (morse code) are synthesised, not loaded from WAVs. Some WAVs are stereo, but the code must handle this or every platform would die. Could it be an endian issue? PPC? Ah, I wonder if I assumed PPC was gone, when porting the code? So you might need to add byte-swapping into the code, if __PPC__ is set. James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On 13 Feb 2013, at 10:05, ys flightg...@sablonier.ch 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 that I had absolutely no problems with alut and 2.8 some months ago. If you're on Intel, and the 2.10 official release works, I am stumped. The code is /extremely/ simple - open file, read some bytes. There's no scripts or options or anything to control it, as far as I know. And there's no mystic endian-ness, and plenty of people on Linux use 32-bit builds - so I really have no idea what might be going. Sorry, not helpful I realise. James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 unofficial fg side release, even when I tried to follow the official release plan with this piece the last months. Maybe it's a simple slave hardware issue, or there is some strange behaviour with the macports setup and I need to hang another machine with a fresh new install into jenkins. As the official mac release has working sound I guess it's really not related to sg/fg code at all, sorry for the noise. And as a launcher without built-in libs FGx still works on macs, also with 2.10. All these things need a lot of time, and many thanks for your support and thoughts. When I installed a jenkins some months ago I thought we can switch version with the new build, skipping a dependency here and there, and build it, release, finish, without a lot of tweaks. Forget that with flightgear (and Yves, and osx, and all this old unused machines) ;-) My last hope is now that I can bring back some findings that are useful for others the next days probably, and that I get a new build that makes FGx 2.10 also possible for mac users. It's not impossible, but I still have no idea why the sound has gone. -Yves Am 13.02.2013 um 11:39 schrieb James Turner zakal...@mac.com: On 13 Feb 2013, at 10:05, ys flightg...@sablonier.ch 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 that I had absolutely no problems with alut and 2.8 some months ago. If you're on Intel, and the 2.10 official release works, I am stumped. The code is /extremely/ simple - open file, read some bytes. There's no scripts or options or anything to control it, as far as I know. And there's no mystic endian-ness, and plenty of people on Linux use 32-bit builds - so I really have no idea what might be going. Sorry, not helpful I realise. James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On Feb 11, 2013, at 03:05 PM, ys flightg...@sablonier.ch 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 activated fg hangs (no segfault). I can only startup with aircrafts that have no engines running (i.e. c172p or b1900), the others will crash flightgear and I get a simgear log entry that the associated wav files are corrupted or truncated. Ehrm, looking where this message is generated there are a lot of possibilities in your new wavreader ;-) Can you give me any hint where this OpenAL sound problem could reside? Strange thing is that avionics sound works (i get some 'instrument beeps' in b1900 i.e.), only the engine is a problem. When I turn off sounds (switching off master in the GUI) everything works as expected, I get 30 fps without shaders and out of KSFO, keys are working etc. Maybe this is not related to 10.5 at all and there are some other important changes/patches for osx compilation I missed after alut nuke ?To be honest I have no ideas - the WAV reading code is extremely simple, and copied directly from the ALUT sources - it's used everywhere - Windows, Linux and Mac, with no #ifdefs. So I can't imagine why some sounds would work and not others. Except, some of our beeps (morse code) are synthesised, not loaded from WAVs.Some WAVs are stereo, but the code must handle this or every platform would die. Could it be an endian issue? PPC?Ah, I wonder if I assumed PPC was gone, when porting the code? So you might need to add byte-swapping into the code, if __PPC__ is set.James-- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On 9 Feb 2013, at 20:49, ys flightg...@sablonier.ch 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/threads/reports where I can see the reason for this decision and where the problems resides ? There's no decision, if you want to keep 10.5 support just send me patches or submit merge requests, that's fine. Personally I have no way to test 10.5, and I don't really think there's many 10.5 Macs which will run FGFS at a usable framerate, but I am happy to be wrong about that! (On the basis that most people who can upgrad to 10.6 or 10.7 would have done so, so it's mostly PPC Macs, which have Radeon-1 class hardware) James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
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 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). I imagine a low budget second or third instance for some scenarios, still with reasonable framerate, but without all the sophisticated graphics, yes. I will send some merge requests, but it's up to you or others to decide if it is worth to have this directives in code, because it's not that longterm perspective probably and it's a bit crazy for well known reason to still support 10.5. Thanks, Yves Am 10.02.2013 um 12:56 schrieb James Turner zakal...@mac.com: On 9 Feb 2013, at 20:49, ys flightg...@sablonier.ch 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/threads/reports where I can see the reason for this decision and where the problems resides ? There's no decision, if you want to keep 10.5 support just send me patches or submit merge requests, that's fine. Personally I have no way to test 10.5, and I don't really think there's many 10.5 Macs which will run FGFS at a usable framerate, but I am happy to be wrong about that! (On the basis that most people who can upgrad to 10.6 or 10.7 would have done so, so it's mostly PPC Macs, which have Radeon-1 class hardware) James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] OSX 10.5 compilation
On 10 Feb 2013, at 13:48, ys flightg...@sablonier.ch 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). I imagine a low budget second or third instance for some scenarios, still with reasonable framerate, but without all the sophisticated graphics, yes. I will send some merge requests, but it's up to you or others to decide if it is worth to have this directives in code, because it's not that longterm perspective probably and it's a bit crazy for well known reason to still support 10.5. If they are really intrusive we could make a fork from 2.10 to apply them, and keep them out of next? But less see before we worry about that! James -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] OSX 10.5 compilation
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 my patch, I just realized that things needs review ;-) ), but I see also some other code i.e. in simgear that doesn't take sdk 10.5 into account anymore (terrasync.cxx and svn version directives i.e.). My question is: Has there been a decision by the core team not to port SDK 10.5 anymore I missed ? When I look to official release announcements I see that Mac version supports = 10.6 since 2.8 ... 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/threads/reports where I can see the reason for this decision and where the problems resides ? Thanks, Yves -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
