Yes, it allows static linking as long as you provide, at least, the
object files to allow the user to link the program with newer versions
of the library.
El 23/3/19 a las 0:38, Nor Jaidi Tuah escribió:
Remember that libvala is distributed under LGPL license, so although
you
can link it dinami
I would imagine that the parameter is not used, it is optimized
according to the yield.
But that would have to be the same with a non-async method.
Nice Day
Wolfgang
Am 07.02.19 um 21:56 schrieb rastersoft:
Hi all:
I did an async function and after a yield I tried to use one of the
parame
If anyone has suggestions for improvement, please use the issues on github
https://github.com/wolfgangmauer/valaDevelop/issues If someone does not
want to post in this list can also send me a PM I would be very happy
about feedback Wolfgang
___
vala-
Hello,
Please correct me if I'm wrong, but I think that if you compile it statically,
it is the same thing as if you change it:
the user cannot fix a bug in libvala and use the modified version instead, for
instance.
Vivien
Le samedi 23 mars 2019 à 11:00 +0100, Wolfgang Mauer a écrit :
> Thank
Thanks for the hint, i do not want to change libvala(that's beyond my
abilities), i am only interested in using a static libvala version and
not one that is installed on the system... Greetings Wolfgang
Am 23.03.19 um 00:38 schrieb Nor Jaidi Tuah:
Remember that libvala is distributed under LGP
>
> Remember that libvala is distributed under LGPL license, so although
> you
> can link it dinamically without problems with any code, free or
> privative, if you do it statically you must allow the users to
> recompile
> it against any version, which means to distribute the source code or,
> a
