Messages

931

Audio / Can't Get Audio To Work in Mac OS

« on: January 13, 2009, 05:50:20 pm »

Hum... what's odd is that the samples were built for Mac OS X 10.5, so the one provided may not have worked on your computer, but they did. And now when you build them yourself for the good OS X version, it does no more work...
And I'm using GCC 4.0 too...


By the way... another Mac OS X Leopard user reported that the audio samples ere working fine. I don't know if it's a Mac OS X 10.4 issue only, I'd need some more feedbacks from other users.

I currently know nothing and I understand nothing about this crash, sorry.

932

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 13, 2009, 05:29:12 pm »

Okay... ^^ Thank you very much .

933

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 12, 2009, 11:21:49 pm »

That would be really helpful, but keep in mind you do not have to do so, it's not an obligation ^^.

934

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 12, 2009, 08:50:47 pm »

Ok, I'll wait for the original poster to answer.

I'm pleased to see that everything seems to be working fine for most people now .

935

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 12, 2009, 04:37:10 pm »

Everything we talked about here should now be fixed.


Could you also have a look at this topic and check whether it's working for you ? http://www.sfml-dev.org/forum/viewtopic.php?p=5846#5846

936

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 12, 2009, 04:11:04 pm »

The working directory is set to the Resources folder when using a bundled application, or the directory containing the executable otherwise.


I think it's better do to the Mac OS X way (that is having all the resources in the bundle) than trying to just follow the Windows one, but of course this prevents the samples from working fine (maybe symbolic links in the Resources directory pointing to the datas folder would do the trick).

Edit: using symbolic links works fine. I added a shell script to make them when building with Xcode. I'll send the changes soon.

937

Audio / Can't Get Audio To Work in Mac OS

« on: January 12, 2009, 02:10:42 pm »

What is your Mac OS X version ? GCC version ?

938

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 12, 2009, 02:10:03 pm »

Andyj, could you try out SFML with the latest SVN version ?

Type this in the Terminal application to get the files :

Code: [Select]

svn cp https://sfml.svn.sourceforge.net/svnroot/sfml

939

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 11, 2009, 05:29:06 pm »

Yep, there will. Too much annoying points in the current version.

940

Audio / Can't Get Audio To Work in Mac OS

« on: January 11, 2009, 05:38:17 am »

Uh... this is... weird.. really, especially if you're using the same source code to make the programs and the same project I used to build them...

And crashing on a alSourcei() call is ... odd :mrgreen: .

I don't have the faintest clue why this happens... :roll:

941

General / Paths and OS X

« on: January 10, 2009, 02:11:55 pm »

It's being discussed there : http://www.sfml-dev.org/forum/viewtopic.php?p=5727#5727

This is a working directory issue. When you launch your app from Xcode, the working directory is set to the folder containing you app, but when launching from the Finder, no working directory is set, and the default one is the root : /.

942

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 10, 2009, 02:03:51 pm »

I'd love to read how you'd tackle the problem.

I'd set the right working directory with chdir(). Then you could read files with paths relative to the resources folder.

This means that I'd like to compile some SFML apps for OS X before SFML 1.5 gets out.

Ok ^^.

943

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 09, 2009, 09:24:46 pm »

The .dmg file does not fix any SFML bug. The frameworks were just malformed.


And.. your solution is... heavy.
If you want the user to use argv, let him at least set the working directory correctly rather than annoying him with an absolute path.

I can get the program path without forcing the user to give me the main() function arguments, this is not a problem. The point is rather choosing to do it or not.

I think I'll actually set the just working directory to the Resources folder at SFML initialization. Let me think about it a few more days (or weeks , anyway the 1.5 release is far away).

944

General / [C++/OSX]two bugs/issues, locale and assets

« on: January 09, 2009, 02:33:12 am »

Really interesting...

And thought I had already been noticing this issue, I could not figure out why it was happening. Your idea sounds useful.

I'mma talk to Laurent about it, thanks !

That was the second problem, the first one was that it couldn't find the data from the "datas" folder, which I solved by moving into the bin directory and ran the samples apps (e.g. opengl.app/Contents/MacOS/opengl).

This could probably be fixed by getting the path of the executable from within the binary files and storing the required files in .app/Contents/Resources/.

Storing the files in the Resources folder won't change anything. When launching the application from the Finder, the "current working directory" is set to /. Therefore, the app won't be able to load the resource files until you put them in the root directory (I admit this is quite annoying...). The solution would be to change the working directory. But... why, why not ?

I talked a little bit about this to Laurent, because it's a Mac OS X issue (I don't know what's the behaving with Linux), and the final conclusion was that "it's the SFML user's work". The main argument is that if SFML does the setting for the user, his would be overwritten, which is unconvenient.

We can talk hours about it, and I'm still not sure what is to be done, that's why I did nothing to fix this.


By the way, I saw you wrote at 1 PM (GMT +1), which means you downloaded the first archive version, a corrupted one (there were broken links in the frameworks). You won't be able to build any SFML application with the provided frameworks until you download the archive again (but actually sound to have built them yourself...).

945

General discussions / SFML 1.4

« on: January 08, 2009, 05:33:48 pm »

The packages have been updated.