Library's name

mike4

Thanks now linking and compiling is ok. but executing at another place I get:
liblin.so => not found
even tough I've copied it into the same folder as the executable. Which leads to another question:
1- how to link statically
2- " dynamic ( having the lib in the same folder )

2-would not allow closed source if the lib is gpl2? So i probably will go something else...

loladiro

You mean concerning the licensing issues?
You have three options:

Don't do it

Get the author to give you a proper license that allows closed source apps

Make your project open source (and GPL)

mike4

Thanks now linking and compiling is ok. but executing at another place I get: liblin.so => not found
even tough I’ve copied it into the same folder as the executable. Which leads to another question:
1- how to link statically
2- “ dynamic ( having the lib in the same folder )

2-would not allow closed source if the lib is gpl2? So i probably will go for something else…
Thanks again, you're very helpful.

loladiro

"About shared library search paths":http://www.eyrie.org/~eagle/notes/rpath.html

giesbert

copying to the same dir only works on windows, not on linux.

mike4

I saw that below with another project. What exactly is that? shared would need some *.so? But there's only the executable shipped.

LNFLAGS+=-shared -rdynamic -nodefaultlibs -m32 -ggdb -L/usr/lib32 -L../libavionics -L../libogl -L$(LUAJIT)/lib

travertinclean

MinGW is a port of GCC - Gnu Compiler Collection to Microsoft Windows. Just Check your configuration process..

mike4

what is that? are u copying loladiro's answer? read my question pls or no better i start a new thread

mike4

the author told me that i dont need to link wheter static nor dynamic and hence no gpl problem....

http://www.osnews.com/story/24557/Torvalds_Android_GPL_Claims_Totally_Bogus_

"It seems totally bogus. We've always made it very clear that the kernel system call interfaces do not in any way result in a derived work as per the GPL, and the kernel details are exported through the kernel headers to all the normal glibc interfaces too. ... If it's some desperate cry for attention by somebody, I just wish those people would release their own sex tapes or something, rather than drag the Linux kernel into their sordid world."

loladiro

So, you want to use the kernel system call interface? Or what do you want to tell us with the link? In the case of the linux kernel headers, the (legal) situation is kinda special, because they contain merely the definition of an interface to interact with the kernel. Is the library you want to use a headers only library?

mike4

have a look at the link to vascore below. I was told that no linking is needed as communication would be alike the link posted above.

mike4

https://github.com/PhilippMuenzel/vascore-embedded

that's what im looking at...

giesbert

Hi mike4,

there are 3 possibilities:

you use plain C functions. Then you can use late binding and QLibbrary::resolve

you want to use C++ classes, then you must use early binding and link against the library

you combine them through the use of interfaces and creator functions. But then the interfaces must be pure interfaces.

mike4

Hi
now i simply want to compile/run the main.cpp in the root folder and get:

dlerror:/apps/X-Plane/Aircraft/General Aviation/Paa/alal/plugins/fmc/lin.xpl: undefined symbol: _ZN9FMSSystemC1Ev

Compilation is ok without linking. So i cannot link for GPL reasons but what am i doing then? And why do i get the above error if i don't have to link?
The lib is compiled and copied into the same folder as the plugin(main.cpp; x-plane plugin) above. Either the lib as the plugin are shared libs.
Thanks again
Michael