I’ve implemented proper project reference support for this for EBuild. I’d love to send you new build in a couple hours to test it (the app bundles look good, but I’m in no position right now to test on device).
What you’ll wanna do when you get the new build is
remove the hard file references between the projects
redraw the projects onto each other (extension onto watchOS app; watchOS app onto iOS app) to have the new fire create actual project references.
EBuild will now handle these cleanly to add the proper bundles into MacPack, including device vs sim, different configurations, etc. (it does the same for Cooper->Island NDK references, btw).
What’s not done (yet) is the IDE doing the extra setup magic to the Info.plists when dragging the projects (but yours should already have that), nor will it “know” that these are especial references, so they’ll probably show as missing/broken in the IDE for now.
I was trying that but I cant work out where to drag it to. For example if I drag the watchos extension to the watchos app the only place it seems to allow dropping is references but that doesnt seem to do anything.
(again, the error message omg the ref is expected for now). it builds cleanly and as everything bundled as it should, as far as I can tell w/o testing on device.
hmm, ok. i’ll check again before tonight’s beta, maybe something else broke/changed after i implemented this, coz it did work for me… i’ll keep you posted.
Confirmed and fixed, something really stupid in there logic for checking what references are valid that I tweaked after implementing this. my apologies.
One thing I did notice is that its updated the CFBundleDisplayName in the watch app and the bundleidentifiers in the elements files. Would it be possible to only do that during project creation ?
I had a terrible time at the beginning getting everything to work.
check then device log in Xcode for a detailed/concrete error. i’m not surprised SOMETHING is still off, we’ll need to figure out what it is. will follow up on the rest tomorrow.
hmm. yeah. i think i might need to rename the WK binary stub to the actual app name… i’ll compare what our v9/msbuild task does; i know EBuild currently does not rename it.
Fixed, along with a couple other CreateAppBundle bugs. I’ll have a new external compiler for you in 30 or so.
it only does that once, when you link the project, as afaik they HAVE to match. The build only sets/changes this value in the Info.plist only if none is specified in the original .plist. Once you set a value there, that will persist/override what goes into the app… What’s the exact problem you’re having?