Doesn't build on QT 4.7 Beta.

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

I'm trying to build QtD on KDE SC 4.5 Beta and DMD 2.047, but it fails:

maxter · Joined: 17 May 2006 Posts: 34

Updated to dmd.2.047 and fixed that VoidFunc error. The thing seems to work but I will be able to test it only tomorrow.

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

Built now, but when trying to compile an example:

SgtMuffles · Joined: 30 Dec 2007 Posts: 1

For the missing Traits.d file, you can copy the one from http://dsource.org/projects/qtd/browser/d2/qtd/Traits.d to /usr/local/include/d/qtd/Traits.d and it should work fine. It did for me.

maxter · Joined: 17 May 2006 Posts: 34

Should have been fixed in http://www.dsource.org/projects/qtd/changeset/367%3Af69341b40588. Please use the latest trunk.

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

OK. Library built. I've written a simple program. It compiles, but does not link - I get a huge output consisting of these:

eldar · Joined: 14 Jun 2008 Posts: 101 Location: Ufa, Russia

Can you post the exact command that you use for building the example?
It should be something like
dmd main.d -L-lqtdgui -L-lqtdcore -L-lcpp_gui -L-lcpp_core -L-lQtGui -L-lQtCore

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

Compiled, but running gives this:

./hello: error while loading shared libraries: libcpp_gui.so: cannot open shared object file: No such file or directory

despite it is present in /usr/local/lib...

EDIT:

Tried a few possibilities, but nothing works :/

What flags do I need to put in /etc/dmd.conf in order to compile programs just with "dmd main.d" even if it uses qtdwebkit, qtdopengl etc.?

EDIT down:
You've post it probably while I was editing my post - I'll try it, but please answer my question also Smile

eldar · Joined: 14 Jun 2008 Posts: 101 Location: Ufa, Russia

It usually happens that it doesn't see libraries from /usr/local/lib . Try to restart your terminal and also check the LD_LIBRARY_PATH environment library, /usr/local/lib should be on it.

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

Yes, it was empty. I've set it using export, but how to store it permanently?

After setting it works, but when I tried to use some oter modules (XML, WebKit, Network etc.), then it doesn't work.

Flags in /etc/dmd.conf:
-I/usr/local/include/d -L-lqtdcore -L-lqtdgui -L-lqtdopengl -L-lqtdnetwork -L-lqtdsvg -L-lqtdxml -L-lqtdwebkit -L-lQtCore -L-lQtGui -L-lQtOpenGL -L-lQtNetwork -L-lQtSvg -L-lQtXml -L-lQtWebKit -L-lcpp_core -L-lcpp_gui -L-lcpp_webkit -L-lcpp_svg -L-lcpp_network -L-lcpp_opengl -L-lcpp_xml

Result: lots of similar to this:

maxter · Joined: 17 May 2006 Posts: 34

You are linking against libcpp_*.so libs corresponding to Qt modules not used in your program. Consequently, the dynamic linker cannot resolve functions referenced by SOs but not present in the host executable. Try to remove the unused ones. This is a temporary limitation that we hope to fix asap.

eldar · Joined: 14 Jun 2008 Posts: 101 Location: Ufa, Russia

Also it's not a good practice to put all possible libraries to link into the dmd.conf. This file should only contain implicit linking to the runtime and the standard library, not any other 3rd party libraries. All the linking business should be a part of particular project build system.

EDIT: of course this doesn't apply if you are using a local dmd.conf.

Mitu · Joined: 22 Sep 2009 Posts: 59 Location: Poland

Maxter, eldar - thanks.

Maxter, your solution works, now everything compiles and links correctly.

One more question: How to set LD_LIBRARY_PATH permanently?

eldar · Joined: 14 Jun 2008 Posts: 101 Location: Ufa, Russia

I don't know how to do it permanently, but for development purposes I put it in ~/.bashrc so that it is set each time you launch terminal. However if you double click on the executable linked to libraries that are there, they won't work, so you'll have to launch them from terminal as well. You may also google or ask someone else more knowledgeable.

Lutger · Joined: 25 May 2006 Posts: 91

You can add the option -L-R/usr/local/lib to compile in the executable itself that it should lookup /usr/local/lib for shared libs. Run 'ldd main' to find out exactly which so's it can and cannot load.

There is usually a configuration file /etc/ld.so.conf where you can specify additional search paths, or a directory /etc/ld.so.conf.d/ where app specific conf files for those paths can be stored. The internet suggests however that LD_LIBRARY_PATH should only be used for development purposes and the -R switch is the preferred way to solve this problem.

I found these links useful:

http://linuxmafia.com/faq/Admin/ld-lib-path.html
http://www.eyrie.org/~eagle/notes/rpath.html

Great to see QtD compile easily by the way, it also works on 64-bit out of the box! (just by setting CXXFLAGS to -m32)