Re: copying OS X binary resources & isfile question

Hi Vaclav

>> more technically there are two other steps in the build process which
>> aren't needed since we are doing bundles :
>> 
>> - the setting of the custom icon with SetFile, setting the type of the
>> single file exe to APPL, done with the  ...__mac_setfilecmd,
>> - the rezzing of .r resource files, done with the ...._mac_rezcmd
> 
> So these two are completely useless when developing (modern apps) for OS
> X? If they are, as I think is the case, then all of this could be
> removed from Bakefile, right?

for bundle based applications yes, but single-file-apps are still supported
on OSX, it's just for wx that we got rid of all dependencies on these older
style resources, so I don't know about whether there are other users of
bakefile on osx which are either still relying on older wx versions or have
integrated their own .r files, but these could just keep using 0.23 I guess
..
 
> In the meantime, is the "SetFile -t APPL binary_filename" call (not
> setting icon, not doing rez) harmful too? If it isn't, then simply
> removing all uses of <mac-res> from wx's bakefiles should be enough.

the problem of SetFile -t APPL is that then again the binary shows up with
the generic application icon (sheet with pencil, ruler etc) and in the
finder info window it claims being a 'classic application' (because the
'carb' resources are missing)...

Best,

Stefan




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/