[5.20] library users

[dobro]

I think it faudrai consider a system that keeps the compatibility of the new version of PureBasic, with older users Libraries

so, it is not obliged to have any recompiling every time ...
especially since we do not necessarily have the sources ...

[Fred]

It's not possible, so you have to recompile them everytime as internals can change as we don't provide compatibily at binary level (especially if you are using a third party tool to create PB libs).

[Little John]

especially since we do not necessarily have the sources ...

I only use 3rd party libraries that I have in the form of source code, so I'm always on the safe side.

[User_Russian]

(especially if you are using a third party tool to create PB libs).

Whether there is an official tool for creating libraries of PB code?

[PB]

Lib makers could just compile their libs as DLLs instead,
so they could be used with ANY version of PureBasic.

[USCode]

Lib makers could just compile their libs as DLLs instead,
so they could be used with ANY version of PureBasic.

Of course then by definition you lose the ability to statically link the library into the executable, which many folks here prefer. Tradeoffs!

[PB]

You can embed the DLL into the final exe and then extract
it to %TEMP% to access it; but as you said, it's a trade-off.

[Thorium]

You can embed the DLL into the final exe and then extract
it to %TEMP% to access it; but as you said, it's a trade-off.

You can also initialize it directly in memory. There is a lib for that: http://www.purebasic.fr/english/viewtop ... 27&t=44091

The trade off is the application size. Staticly linking a lib results in a much smaller executable.

[Kwai chang caine]

Whether there is an official tool for creating libraries of PB code?

I believe they talk about TAILLEBITE, but it's not an official tool

[dobro]

but ... if we had the ability to color our gadgets and window with Purebasic .... I will not be using already PureColor of Gnozal