Pods prefix file generation

[fgarcia]

I am having a problem with a change in how the pods prefix header file is being generated. It seems that recently, the prefix generation is no longer in the same order as in the Podfile. For example, if I write

pod Lib_B
pod Lib_A

The generated Pods prefix file looks like this:

#import "Lib_A.h"
#import "Lib_B.h"

I understand that not all pods modify the pods prefix file, but I am having problems now with the new generation order. In my case, because of some macros within "Lib A", its compilation will be different if it is detected that "Lib B" is available.

This situation might not be common, or even considered "bad practice". I am not sure if it is a good idea making the Podfile DSL declaration order sensitive. Maybe a better solution could be a way to add my own macros to the prefix file before anything else is generated. However it seems that currently the Podfile DSL does not support that.

For example, I would like to write in my Podfile as I do in my specs:

 prefix_header_contents = <<-head
       #import "Lib_B.h"
       #import "Lib_A.h"
  head

That way, the imports will be repeated later, but at least, I had the chance to do them in the right order.

How could this problem be solved?

[fabiopelosin]

Moving this to #833 which should solve your problem.