Application icon for Linux

[Relfos]

I see, but does that means that the package needs to include the source?
This is a comercial project, also available for other platforms, so I don't want to release the source for now.
Right now I've simply put the compiled executable along with the resource files in a tar.gz file, would there be any problem with this approach?

[code_glitch]

Unless I am mistaken you could just include the .a and .o file and then just do the linking on the target - I recall some closed source codecs and etc worked that way...

In your instance (executable in tar.gz) I guess you would just have to link it dynamically and hope for the best - just be warned that if any bugs arise with this setup, you cant ask for compiler messages and you may end up having a super fun time with clients... Or at least thats my experience with the last Ludum dare fiasco.

[Andru]

I see, but does that means that the package needs to include the source?

If you don't use libraries with GPL-like license(or LGPL with static linking) - then no need to include source code. For Linux rules of opening source code is the same as for other platforms

[cairnswm]

I do not use Linux so my suggestion could be hopelessly wrong.

Could your executable not create the icon in the correct directory(ies) on first run? So the executable starts up, checks in the directory for the icon file, if it does not find it, creates/copies it and carries on.

As part of your install process/instructions you could just execute the program once to create the icons.

[Andru]

Could your executable not create the icon in the correct directory(ies) on first run?

Can't, because writing to / needs root privileges

[cairnswm]

So how does an installer copy files there?

[Andru]

So how does an installer copy files there?

Installing packages also needs a root privileges, but in this case system will ask user about a password. Linux and MacOS X are not a Windows where you can setup any <censored> in your system(with by default settings)