Linked by Thom Holwerda on Wed 6th Jun 2007 20:30 UTC, submitted by Eskil A. Blomfeldt
Permalink for comment 245911
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2005-07-07
Yes, the libraries need to be present at application runtime, so they can either be installed separately or come bundled with the applications.
On Windows and Mac OSX the second option is usually preferred, though, similar to the Java Runtime Environment, it would be possible to install it only once into a system directory.
I am not sure this is the most usueful angle to look at it. I think the main question is: what advantages might Qt Jambi bring to the average Qt developer over C++
Examples would be:
- crossplatform IDE support through the Eclipse plugin
- huge number of Java utility libraries
- comparably trivial plugin handling (Class.forName vs. C based dlopen/dlsym)