LOG_LEVEL_DEF is no longer defined after CocoaPod Update

[Randy Fong]

Problem with CocoaLumberjack after running CocoaPod update.

I ran the following CocoaPod update.

Installing CocoaLumberjack 2.0.0-beta (was 1.9.0)
Installing CocoaLumberjack 1.9.2 (was 1.9.0)

and now my legacy IOS app is compiling with an error.

The variable LOG_LEVEL_DEF is no longer defined.

#define LOG_ERROR   (LOG_LEVEL_DEF & LOG_FLAG_ERROR)

Anybody else running into this problem? Any suggestions?

[Joe Francia]

Change every instance of...

#import “DDLog.h”

...to...

#import <CocoaLumberjack/CocoaLumberjack.h>

This fixed it for me in 2.0.0.

--
You received this message because you are subscribed to the Google Groups "CocoaLumberjack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cocoalumberja...@googlegroups.com.
To post to this group, send email to cocoalu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cocoalumberjack/487e2564-8825-41e1-b97a-5a67c0b4a570%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Randy Fong]

Thanks for the suggestion Joe!

Looking at the the change that CocoaPods made to the CocoalumberJack modules, it looks like it implemented a new folder "Classes" and that folder contains the updated files that used to be in the  "CocoaLumberjack" folder.

On the surface, it seems like the "CocoaLumberjack" is being deprecated and replaced by the "Classes" file.

The problem seems to be what is being referenced to in "Pods/Pods/Lumberjack/Core/DDLog.h".

The version in core doesn't have the variable.

So the questions is....

What needs to be changed when running cocoapods or defining paths in lumberjack, so that the Classes Folder updates the Core folder in xcode?

BTW. Looking at the "README.MD" it mentions your solution of changing the import definition, but that is a very confusing way to go especially when you are looking at the source code in the Core folder.