Page 1 of 2
Libraries announcements
Posted: Thu Oct 02, 2008 8:33 am
by DoubleDutch
Gnozal: Is it possible for you to compile an early release of your libs, so people can try compiling projects that use your libs on PB4.30?
Thanks
Re: PB 4.30 beta versions of Gnozals libs please...
Posted: Thu Oct 02, 2008 1:39 pm
by gnozal
DoubleDutch wrote:Gnozal: Is it possible for you to compile an early release of your libs, so people can try compiling projects that use your libs on PB4.30?
Sorry, but I will release new versions for PB4.30 final only, as previous PB versions have shown that libs may be broken from one beta to another (and I do not have much spare time for the moment (so maybe I change my mind when I have more free time)).
And only x86 libs, as I don't have a 64bits OS.
Thanks.
Posted: Fri Oct 03, 2008 12:11 pm
by Thalius
What could work is:
Install some Linux 64 bits and run the windows x64 PB under wine
At least the 32 bits version runs. Will have to try at home on the x64.
That way no special win license would be needed.
just an idea
Thalius
Posted: Fri Oct 03, 2008 6:21 pm
by X
Also you can get the 120 day trial of Windows 2008 64Bit for compiling on ....
and its 100% free from microsoft ....
PURE... Libs Error with PB 4.40 Beta 1
Posted: Mon Aug 17, 2009 11:20 am
by Donald
Hi gnozal,
the Error
Code: Select all
POLINK: error: Unresolved external symbol 'SYS_AllocateString'.
POLINK: fatal error: 1 unresolved external(s).
also come with the other Userlibs.
I Use
PureLVSORT
PureRESIZE
PureCOLOR
Donald
..
Posted: Mon Aug 17, 2009 9:22 pm
by Donald
Hi gnozal,
Thanks for new Compiling for 4.40.
Donald
..
All libs updated for PB4.40 beta ... again ...
Posted: Tue Aug 18, 2009 11:57 am
by gnozal
So, I have recompiled most of my libs with PB4.40 beta.
Links as always in each thread (1st post) or on my site.
Posted: Tue Aug 18, 2009 3:58 pm
by localmotion34
Was there a need to recompile the libs? Most times I find that they don't require recompiling unless the userlib format changes.
I have PB 4.3 working perfectly, and I was just wondering if 4.4 would break any backward userlib compatibility?
Posted: Tue Aug 18, 2009 4:10 pm
by gnozal
localmotion34 wrote:Was there a need to recompile the libs? Most times I find that they don't require recompiling unless the userlib format changes.
Yes, PB4.30 'tailbiten' userlibs may trigger a POLINK 'SYS_AllocateString' error when used with PB4.40 beta 1/2.
Posted: Wed Aug 19, 2009 8:42 am
by gnozal
I have updated the PB4.40 beta libs, because the help support was broken.
It seems that unlike previous versions, the current tailbite adds '.chm' to the defined help file.
So with '/CHM:PureCOLOR.CHM' it ends up with 'PureCOLOR.CHM.chm' in the compiled userlibrary.
I have recompiled the libs without '.chm' extension for the help file.
Posted: Wed Aug 19, 2009 6:51 pm
by ABBKlaus
gnozal wrote:I have updated the PB4.40 beta libs, because the help support was broken.
It seems that unlike previous versions, the current tailbite adds '.chm' to the defined help file.
So with '/CHM:PureCOLOR.CHM' it ends up with 'PureCOLOR.CHM.chm' in the compiled userlibrary.
I have recompiled the libs without '.chm' extension for the help file.
Should be fixed in one of the next versions of TailBite
Posted: Thu Aug 20, 2009 7:45 am
by gnozal
ABBKlaus wrote:Should be fixed in one of the next versions of TailBite
Great, thanks !
Re:
Posted: Wed Sep 16, 2009 11:16 am
by UserOfPure
Hi, I just downloaded your updated libs for Beta 3 but it doesn't let me specify the install folder for PureBasic. It says PureBasic is installed in C:\Program Files\PureBasic, but that's version 4.31. I have version 4.40 Beta 3 installed in C:\Program Files\PureBasic440. So you should update your installers to allow the user to change the location.
Re: Re:
Posted: Wed Sep 16, 2009 11:55 am
by gnozal
UserOfPure wrote:Hi, I just downloaded your updated libs for Beta 3 but it doesn't let me specify the install folder for PureBasic. It says PureBasic is installed in C:\Program Files\PureBasic, but that's version 4.31. I have version 4.40 Beta 3 installed in C:\Program Files\PureBasic440. So you should update your installers to allow the user to change the location.
1. The installers look for the PB path in the registry. Please run PB 4.40 Purebasic.exe once (to register the PB 4.40 purebasic path) and try again.
2. You can already choose any folder you want : click on the 'Install...' button and change the target directory.
Re: Re:
Posted: Wed Sep 16, 2009 12:00 pm
by UserOfPure
Hi, for #1 i thought PureBasic would set the location in the Registry when installing the beta, but obviously it doesn't change it. This is a bug then that needs fixing; I will post a report for the team.
For #2 i see what you mean.
I didn't click Install before because I thought it would instantly start installing files at the location shown (ie. the old location). Now I see it prompts for a new location. Is there a way to mention to the user that he can change the location after clicking Install, so as not to panic them like it did me?