Re: copying OS X binary resources & isfile question

Hi

On 05.08.08 12:18, "Vaclav Slavik" <[email protected]> wrote:

> On Tue, 2008-08-05 at 11:49 +0200, Stefan Csomor wrote:
>> 1. why does the following work in the hello.bkl
> 
> It doesn't, not with the autoconf format.

what exactely is not working ? I have the following findings:

bakefile -f gnu hello.bkl

with a hello.bkl that has a

<set var="TEST_VARIABLE">
  <if cond="$(os.path.isfile(SRCDIR+'/hello.c'))">
    $(SRCDIR+'/hello.c')
  </if>
  <if cond="$(not os.path.isfile(SRCDIR+'/hello.c'))">
    $(SRCDIR+'/another_hello.c')
  </if>
</set>

allows me eg to use this TEST_VARIABLE

in a             

<sources>$(TEST_VARIABLE)</sources>

clause, I've tested both situatations, if I do a rename of hello.c to
another_hello.c and rebake the GNUmakefile is adapted accordingly
 
>> 2. another OS X problem, unrelated to the vars above :
>> 
>> Currently we still have the single file executable built and then a .app
>> bundle built beside, in the end we link from Contents/MacOS/$(id) from the
>> bundle back to the executable, but this gives some people problems,
> 
> A little bit of specificity wouldn't hurt here...

ok, I thought you were aware of it, so I didn't want to elaborate on
something known: currently eg for the minimal sample the app is built once
as a single file ./minimal , in the finder this is the file with the old wx
icon. (This is the file that doesn't receive input when double clicked,
that's what people complain about on the list). Then the bundle is built and
in the mac_bundles.bkl we have the lines :

<!-- make a hardlink to the binary: -->
ln -f $(ref("__targetdir",id))$(ref("__targetname",id))
$(BUNDLE)/MacOS/$(id)

so ./minimal.app/Contents/MacOS/minimal links to ./minimal and the
minimal.app in the finder shows the new icon, can be double-clicked and
works w/o a problem

and what I'd like to achieve is to have the executable being built in
minimal.app/Contents/MacOS from the start

>> can we just change the destination for the exe to be INSIDE Contents/MacOS
>> from the
>> start ?
> 
> Not easily and without additional problems, I think. You may want to try
> setting <dirname> to something dynamically determined.

ok I'll try that

Thanks,

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=/