OK, I tried the *_STANDARD_INSTALL = no. Works like a charm. So does *_COPY_INTO_DIR, but I'm torn with this one. Using Ivan's solution I have only one rule, one section of one file to change when needed. with *_COPY_INTO_DIR, I have to spread it into all make files it applies to. It's OK for *_STANDARD_INSTALL, which is mean to affect only that bundle itself, but the other one is meant to affect the whole build. I think I'll stay with Ivan's solution as it's much more maintainable. Thanx guys!
On Wed, Feb 15, 2017 at 6:17 AM, Wolfgang Lux <[email protected]> wrote: > >> Am 15.02.2017 um 02:17 schrieb Jamie Ramone <[email protected]>: >> >> Thanks for that bit of advice, but since it was getting on my nerves I >> removed all PC related files from my project and just maintain the >> makefiles by hand. Ivan's solution seems to work well enough so I'm >> going with that. One thing I can't seem to get around is that >> gnustep-make installs the bundles in the installation domain. I only >> want to copy them into the application proper, which I'm already >> doing. Can the install target be turned off for those individual >> bundles? > > As Matt Rice already suggested in an earlier mail, use foo_COPY_INTO_DIR in > the GNUmakefile where your bundle is built (replacing foo by the name of your > bundle of course) and use the (relative) path to the directory where your > application is built as target. For instance, if you build both MyApp and > MyBundle from the same makefile you would use > MyBundle_COPY_INTO_DIR = ./MyApp.app > in the GNUmakefile. If you build the bundle and/or application inside a > subproject you have to adjust the path accordingly. > > Hope this helps, > Wolfgang > > PS You don't need any extra rule in GNUmakefile.postamble with this setup. _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
