Undefined symbols when linking with liblcf on OSX about editor HOT 16 CLOSED

Are you trying with latest liblcf from Git? 0.2 release is outdated to build Editor from Git. There are a few details to build and install liblcf here, however they are not updated and may need more steps. If you have issues yet I'll try again to build it from my OSX VM this week.

Try with a different prefix, maybe is not the right place (I'm not pro with OSX development). I also had some issues to generate the .dylib from libtool.

Feel free to update the wiki if you find a proper way to install liblcf.

from editor.

Well, now I’ve got a new problem: QMake is complaining Project ERROR: liblcf development package not found, even though liblcf is there (I have verified that its *.pc file is on the $PKG_CONFIG_PATH and that QMake is looking for it by parsing the output of qmake -d). What’s going on?

from editor.

Maybe some generated paths inside the .pc file are wrong and not pointing to the right headers or libs. Which is the content of the liblcf.pc file? Are these locations fine? If not, try editing it to point to the proper ones.

from editor.

Here is my liblcf.pc. Note that I have installed liblcf using Homebrew, so the file in /usr/local/lib/pkgconfig is actually a symlink to /usr/local/Cellar/liblcf/1.0/lib/pkgconfig. Will that mess anything up? I’ve confirmed that the symlink isn’t the source of the problem.

from editor.

After removing the symlink, did you try to add this path to the PKG_CONFIG_PATH?

from editor.

My $PKG_CONFIG_PATH is set in my shell profile; it has always pointed to the directory containing liblcf.pc.

from editor.

I figured it out. I need to put a different path (the one for icu4c’s .pc file) on my $PKG_CONFIG_PATH. The error reporting points a finger at liblcf.pc not being found, but what’s really not being found is icu4c.pc.

from editor.

Unfortunately, Editor still won’t link. Same issue (missing symbols from libliblcf.a) as before.

from editor.

Could you pastebin/gist the errors?

from editor.

Here it is. Note that I have modified the Makefile to print the command line being run, in case it helps.

from editor.

Just in case, did you try -llcf instead of -lliblcf?

from editor.

Yes, I did; many times in fact. No luck. In fact, ld complains it can’t even find the library when I do it that way.

from editor.

Try setting LDFLAGS env var with -L/absolute/path/ or ensure the .a folder is fine or symlnked as a recognized library path

from editor.

No good.

from editor.

Well, I finally figured it out. I ended up having to remove liblcf.a from the linkline and add all of the source files that go into liblcf to Editor’s linkline directly. Then it links. Unfortunately, Editor is full of bugs, and does nothing but crash when I try to use it. Oh, well.

from editor.

My thoughts about this issue:

• In the .pro file there is the path to liblcf hardcoded. For my Arch Linux package I disable that behavior and use the shared lib.
• If you make any changes to that .pro file, you need to re-run qmake.
• You need to copy the template folder to the directory you launch the editor from (without it segfaults under linux too).
  Hope this helps a bit, if you try building it again in the future.

from editor.