[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #24613] make overwrites bundles Info-gnustep.plist

From: Nicola Pero
Subject: [bug #24613] make overwrites bundles Info-gnustep.plist
Date: Mon, 20 Oct 2008 21:01:28 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2008092418 CentOS/3.0.2-3.el5.centos Firefox/3.0.2

Follow-up Comment #3, bug #24613 (project gnustep):

Hi Michael

let me explain - it's not documented that well ;-)

In theory, you should have a EnergyConverterInfo.plist file
containing the custom entries for your bundle.  gnustep-make 
will automatically read it, and merge it with the auto
configured fields, and create Info-gnustep.plist. ;-)

So one option you have is to reorganize to follow that schema:
so, you'd remove the lines

EnergyConverter_RESOURCE_FILES = 

from your GNUmakefile, and you'd rename your Resources/Info-gnustep.plist
into EnergyConverterInfo.plist.  Then, do 
a 'make clean' and a 'make' and the file
should be automatically generated containing your entries.

That is the "official" way of adding new entries to 
Info-gnustep.plist, so it should obviously work both with
2.0.4 and 2.0.6. :-)

Of course, I do understand what you are trying to do ...
ie, to completely override this system and just overwrite
the generated Info-gnustep.plist file altogether 
with your own. :-)

If you want to do that, you should use your own rules to shield
yourself from changes in the internal gnustep-make rules.  You
could remove the lines 

EnergyConverter_RESOURCE_FILES = 

from your GNUmakefile, and instead add a GNUmakefile.postamble
with the following code:

        cp Resources/Info-gnustep.plist

(there is a TAB before the 'cp')

In other words, you do the overwriting yourself in your own
rule after the bundle has been built.  Then you're safe that
no matter how the gnustep-make internals change, your code
does not depend on them and should always work :-)

The solution you choose would depend on your taste obviously :-)

The problem you are having with your current code depends
on the fact that there are two internal parts of gnustep-make
trying to generate the same Info-gnustep.plist file: the
xxx_RESOURCE_FILES and the code that generates 
In 2.0.4, the xxx_RESOURCE_FILES copy happened after creating
the file, in 2.0.6 it happens before.  That's just down to
chance ... that order is not part of the public API. :-(

None of the two solutions I proposed above are down to chance
though - they should work reliably on all past, present and
future versions of gnustep-make :-)



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]