⚠ This page contains old, outdated, obsolete, … historic or WIP content! No warranties e.g. for correctness!
All 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
In my recent entry, I already talked a bit about pkg-config and its framework support. It turns out that there is another problem. The --libs parameter can be "split" into its parts by using --libs-only-L, --libs-only-l, and --libs-only-other. The LyX configure script, however, did not care about the latter, only the first two. Which brings me to the mail I wrote to the pkg-config mailing list:
"Hi,
"while compiling LyX/Mac the other day, I came across a problem in the way frameworks are handled. On Mac OS, frameworks are a different way to pack a library together with its headers. Framework-related options are put in --libs-only-other, while the configure script was only checking for --libs-only-l and --libs-only-L. While I agree that this is broken behavior, it brings me to my question:
"The way I see it, -Fpath (framework search path) is equivalent to -Lpath for libraries. Thus, -F should maybe be included in the output of "pkg-config --libs-only-L". The same thing goes for the "-framework name" linker option, which is more or less the same thing as "-lname", namely linking against a certain library/framework. Thus, the -framework option (with argument) should be added to the output of --libs-only-l.
"Opinions?"
In other news, FrOSCon has it second and last day today. I am currently in the train on the way. The party ("social event") yesterday was quite good, even though the weather was not as good as last year—it was cold and humid.