search

drewmccormack / ensembles

A synchronization framework for Core Data.
MIT License
1.63k stars 131 forks source link

Manually installation: libensembles_ios.a library missing #137

Closed Spokane-Dude closed 10 years ago

Spokane-Dude commented 10 years ago

Following the instructions for Manually installing in XCode, the library _libensemblesios.a is missing.

In addition, during the build, I'm getting an error from this script:

PhaseScriptExecution Run\ Script /Users/rm/Library/Developer/Xcode/DerivedData/Ensembles_iOS-fkcndmyqteddajevypymrtsohxfv/Build/Intermediates/Ensembles\ iOS.build/Debug-iphoneos/Documentation.build/Script-072C2F3618C9FBD900453E78.sh

giving me the following build error:

/Users/rm/Library/Developer/Xcode/DerivedData/Ensembles_iOS-fkcndmyqteddajevypymrtsohxfv/Build/Intermediates/Ensembles iOS.build/Debug-iphoneos/Documentation.build/Script-072C2F3618C9FBD900453E78.sh: line 2: /usr/local/bin/appledoc: No such file or directory
drewmccormack commented 10 years ago

If drag the Ensembles iOS project into your app, it should setup the search paths to find the library.

To build the documentation, you need to have the appledoc tool installed. It is a separate project on GitHub.

Spokane-Dude commented 10 years ago

It doesn't exist... if I do a search for _libensemblesios.a in Finder, it comes up with 0 files found.

I'll install the appledoc tool which should take care of the other... thanks for the quick respoonse. :D

drewmccormack commented 10 years ago

The library will only exist after you build the Ensembles iOS project. Have you tried that?

Maybe try that first, and then add it to your project.

Drew

On 25 Apr 2014, at 18:44, Spokane-Dude notifications@github.com wrote:

It doesn't exist... if I do a search for libensembles_ios.a in Finder, it comes up with 0 files found.

I'll install the appledoc tool which should take care of the other... thanks for the quick respoonse. :D

— Reply to this email directly or view it on GitHub.

Spokane-Dude commented 10 years ago

I tried doing the build, which is when I got the appledoc error... I'll try to fix that by installing appledoc...

Would it be possible for you to mention in the docs under Manual Install that the lib has to be build, or some such wording... It's not obvious, although I'm probably the only one who had the problem. I like things to be concise when following directions. :D

Thanks, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 9:53 AM The library will only exist after you build the Ensembles iOS project. Have you tried that?

Maybe try that first, and then add it to your project.

Drew

On 25 Apr 2014, at 18:44, Spokane-Dude notifications@github.com wrote:

It doesn't exist... if I do a search for libensembles_ios.a in Finder, it comes up with 0 files found.

I'll install the appledoc tool which should take care of the other... thanks for the quick respoonse. :D

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41414752.

drewmccormack commented 10 years ago

You should choose the ensembles ops target to build. I suspect you had the documentation target selected.

I'll check the Readme.

Drew

On 25 Apr 2014, at 19:03, Spokane-Dude notifications@github.com wrote:

I tried doing the build, which is when I got the appledoc error... I'll try to fix that by installing appledoc...

Would it be possible for you to mention in the docs under Manual Install that the lib has to be build, or some such wording... It's not obvious, although I'm probably the only one who had the problem. I like things to be concise when following directions. :D

Thanks, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 9:53 AM The library will only exist after you build the Ensembles iOS project. Have you tried that?

Maybe try that first, and then add it to your project.

Drew

On 25 Apr 2014, at 18:44, Spokane-Dude notifications@github.com wrote:

It doesn't exist... if I do a search for libensembles_ios.a in Finder, it comes up with 0 files found.

I'll install the appledoc tool which should take care of the other... thanks for the quick respoonse. :D

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41414752.

— Reply to this email directly or view it on GitHub.

Spokane-Dude commented 10 years ago

Yes, that was it... apparently the Documentation was checked before you uploaded it to GitHub... thank you...

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 10:10 AM You should choose the ensembles ops target to build. I suspect you had the documentation target selected.

I'll check the Readme.

Drew

On 25 Apr 2014, at 19:03, Spokane-Dude notifications@github.com wrote:

I tried doing the build, which is when I got the appledoc error... I'll try to fix that by installing appledoc...

Would it be possible for you to mention in the docs under Manual Install that the lib has to be build, or some such wording... It's not obvious, although I'm probably the only one who had the problem. I like things to be concise when following directions. :D

Thanks, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 9:53 AM The library will only exist after you build the Ensembles iOS project. Have you tried that?

Maybe try that first, and then add it to your project.

Drew

On 25 Apr 2014, at 18:44, Spokane-Dude notifications@github.com wrote:

It doesn't exist... if I do a search for libensembles_ios.a in Finder, it comes up with 0 files found.

I'll install the appledoc tool which should take care of the other... thanks for the quick respoonse. :D

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub

https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41414752.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41416471.

Spokane-Dude commented 10 years ago

Hi Drew... there is NO Ensembles Headers folder... is it somewhere other than the Ensembles project?

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 10:31 AM

Closed #137 https://github.com/drewmccormack/ensembles/issues/137.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137.

drewmccormack commented 10 years ago

No, just add the Framework folder to your header path.

On 25 Apr 2014, at 21:24, Spokane-Dude notifications@github.com wrote:

Hi Drew... there is NO Ensembles Headers folder... is it somewhere other than the Ensembles project?

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 10:31 AM

Closed #137 https://github.com/drewmccormack/ensembles/issues/137.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137.

— Reply to this email directly or view it on GitHub.

Spokane-Dude commented 10 years ago

Hi Drew... I don't know if you want me to contact you directly or post these as "issues" on GitHub... let me know, please.

I am getting a build error on this statement:

 CDEPersistentStoreEnsemble *ensemble =

[[CDEPersistentStoreEnsemble alloc] initWithEnsembleIdentifier:@"salonbook"

persistentStorePath:storeURL

managedObjectModelURL:modelURL

cloudFileSystem:cloudFileSystem];

The error is:

AppDelegate.m:100:81: No visible @interface for 'CDEPersistentStoreEnsemble' declares the selector
'initWithEnsembleIdentifier:persistentStorePath:managedObjectModelURL:cloudFileSystem:'

I have tried everything I can think of, and it still exists. What's wrong? or what else do I have to do?

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 12:25 PM No, just add the Framework folder to your header path.

On 25 Apr 2014, at 21:24, Spokane-Dude notifications@github.com wrote:

Hi Drew... there is NO Ensembles Headers folder... is it somewhere other than the Ensembles project?

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 25, 2014 at 10:31 AM

Closed #137 https://github.com/drewmccormack/ensembles/issues/137.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41430321.

Spokane-Dude commented 10 years ago

In the book, you have the following bit of code:

//Setup Ensemble cloudFileSystem=[[CDEICloudFileSystem alloc] initWithUbiquityContainerIdentifier:@"XXXXXXXXXX.com.yourcompany.yourapp"];

ensemble=[[CDEPersistentStoreEnsemble alloc] initWithEnsembleIdentifier:@"YourStoreIdentifier" persistentStorePath: storeURL <----------- I believe this should be persistentStoreURL, not persistentStorePath managedObjectModelURL:modelURL cloudFileSystem:cloudFileSystem];

Regards, Rolf

drewmccormack commented 10 years ago

Thanks. We changed that, and I guess I missed it. Will fix.

Drew

On 26 Apr 2014, at 00:50, Spokane-Dude notifications@github.com wrote:

In the book, you have the following bit of code:

//Setup Ensemble cloudFileSystem=[[CDEICloudFileSystem alloc] initWithUbiquityContainerIdentifier:@"XXXXXXXXXX.com.yourcompany.yourapp"];

ensemble=[[CDEPersistentStoreEnsemble alloc] initWithEnsembleIdentifier:@"YourStoreIdentifier" persistentStorePath: storeURL <----------- I believe this should be persistentStoreURL, not persistentStorePath managedObjectModelURL:modelURL cloudFileSystem:cloudFileSystem];

Regards, Rolf — Reply to this email directly or view it on GitHub.

Spokane-Dude commented 10 years ago

Hi Drew... another question that I could not find the answer to in the book...

Q: can Ensembles be used just to backup the CoreData store? For instance, if the user accidentally deletes the app, the store is gone also. Can Ensembles be used in this case to restore the store? The reason I ask is that I'd like to roll this out in two phases: backup and sync.

Regards, Rolf

drewmccormack commented 10 years ago

Yes, you could do that. It is just sync with a single device. If you lose the original store, just leech with an empty store, and the data should come back.

But you might find that just copying the store takes less disk space.

It would be a good test case though, for a two phase roll out.

Drew

On 27 Apr 2014, at 17:00, Spokane-Dude notifications@github.com wrote:

Hi Drew... another question that I could not find the answer to in the book...

Q: can Ensembles be used just to backup the CoreData store? For instance, if the user accidentally deletes the app, the store is gone also. Can Ensembles be used in this case to restore the store? The reason I ask is that I'd like to roll this out in two phases: backup and sync.

Regards, Rolf — Reply to this email directly or view it on GitHub.

Spokane-Dude commented 10 years ago

Thanks for the speedy reply... I'll do that and keep you posted... also, thought you might want to know there is an error in the book:

Regards, Rolf

Drew McCormack mailto:notifications@github.com April 27, 2014 at 8:05 AM Yes, you could do that. It is just sync with a single device. If you lose the original store, just leech with an empty store, and the data should come back.

But you might find that just copying the store takes less disk space.

It would be a good test case though, for a two phase roll out.

Drew

On 27 Apr 2014, at 17:00, Spokane-Dude notifications@github.com wrote:

Hi Drew... another question that I could not find the answer to in the book...

Q: can Ensembles be used just to backup the CoreData store? For instance, if the user accidentally deletes the app, the store is gone also. Can Ensembles be used in this case to restore the store? The reason I ask is that I'd like to roll this out in two phases: backup and sync.

Regards, Rolf — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/drewmccormack/ensembles/issues/137#issuecomment-41499022.