Re: [CMake] copy_resolved_item_into_bundle doesn't copy when I want it to

2010-12-21 Thread David Cole
copy_resolved_item_into_bundle only skips the copy if the file to be copied and the destination file refer to exactly the same file. In that sense, it already is a copy_if_different. On the Mac, after a bundle is created and fixed up for the first time, all the references from one library to

Re: [CMake] copy_resolved_item_into_bundle doesn't copy when I want it to

2010-12-21 Thread Ben Medina
That sounds fine. However, I have install rules located in multiple files; my project contains multiple apps, and each apps has its install rules in its own lists file. Where do I put my delete bundle install code to ensure that it runs before all other install commands? Thanks, Ben On Tue, Dec

Re: [CMake] copy_resolved_item_into_bundle doesn't copy when I want it to

2010-12-21 Thread David Cole
I would think immediately before the first install rule that installs the bundle itself or something into the bundle location (assuming you have such a thing). Otherwise, simply before whatever it is that initially creates the bundle on which you are calling fixup_bundle... On Tue, Dec 21, 2010

[CMake] copy_resolved_item_into_bundle doesn't copy when I want it to

2010-12-20 Thread Ben Medina
Hello all, I'm using fixup_bundle as part of my installation rules. One problem I've run into is that if you build the install target multiple times, fixup_bundle (or, more specifically, copy_resolved_item_into_bundle) won't copy a library over if it's coming from the same location. This causes a