next »

[BlueSweatshirt]

Note: this applies to windows, Mac os x, and Linux
I'm doing my first project compiling with makefiles and compiler commands rather than an IDE. I've encountered the problem that my output executables always launch through a command-line, which has been problematic. Should I be using a compiler other than g++ to achieve this? Are there some flags I'm missing? Furthermore on Mac the compiled application is referred to as a "Unix Executable" and not a native Application. I have a strong feeling I'm more than a bit off the mark here--can anyone lead me in the right direction?

[rivon]

Post the commands you're using.

[zacaj]

Mac Executables need to be packaged as apps.  An app is actually a folder with a certain structure, including the executable

[ThemsAllTook]

If you put your Mac executable in a directory structure like this, it'll launch from Finder: MyApplication.app/Contents/MacOS/MyApplication

You may also want to put an Info.plist and PkgInfo in Contents.

For Windows, you need to pass -mwindows to the linker. Not sure about Linux, it's always worked for me in Ubuntu to just open the executable.

[marksands]

I'm no windows guru, but if you want to suppress the command line on windows, try adding this line in your project file:

Code:

// Disable console on WIN_32

#if defined(__WIN32__) || defined(_WIN32)
#pragma comment(linker, "/subsystem:\"windows\" \
/entry:\"mainCRTStartup\"")
#endif

[BlueSweatshirt]

Alright, another related issue:

When I run the SFML executable(be it via app package or otherwise) it'll crash for not being able to locate the resource files the game is looking for. Turns out it's some terminal execution directory issue because when I cd to the binary directory(where the resources are also located) and run the app from terminal it'll find the resources just fine.

Ideas?

[Mikademus]

Obtain the executable location and always provide full paths to your resources. See here:
http://www.cplusplus.com/forum/general/11104/

[BlueSweatshirt]

Haha... Of course. 
Thanks!

[Average Software]

Be extremely cautious about using argv[0] for this sort of thing.  argv[0] is the command used to execute your program, which doesn't necessarily have anything to do with its location, or even the actual binary.

If someone makes a link or shortcut to your program and executes it using that, argv[0] will be the path to the link/shortcut.  This has burned me in the past.

The best Mac way I've found to switch to your resources directory is this:

Code:

NSFileManager *fm = [[NSFileManager alloc] init];
   
[fm changeCurrentDirectoryPath:[[NSBundle mainBundle] resourcePath]];

[fm release];

[BlueSweatshirt]

Alright, I'll do that.
I was hoping to keep a single code base for all platforms, but at this point it looks like it's in my best interests to work with some platform specific code too.

[Average Software]

I was hoping to keep a single code base for all platforms,

I used to do that too, but then I realized that it's far easier to use a back-end/front-end system.  I keep a platform neutral back-end that probably contains 95% of my code, and write platform specific front-ends to interface with it.  Much easier to deal with in the long run.