I completely agree with LaurieT. It seems mad to me that even having all the dependencies installed and confirming the checker script most of the example source code fails to even compile (well... that's once you get the compiler actually loading) - and I'm running on a bog-standard Ubuntu 9.04 distro so it's hardly an uncommon build (other than my custom boot-screens, etc).
Much like Laurie I don't have the time, resources (and basically will) to debug and trace the problems with PB under Linux, but it's definately a problem area. So much so that I'm...

*cough* actually considering running PB under WINE just to get progging again. And that is just insane!
I don't know about others, but my experience with PB on Linux is that even when you've got it running and complining the IDE seems to "pick up"
some of the Libs but seems to miss a shed-load of others, hence the problems with "missing" Constants, etc. I can live with Win API functions, but when "#PB_Example_Code_Constant" or a generic function is unrecognized it's just "too much like hard work".
I fully realise that building and maintaining a PB.deb would be full-time job in itself, but my (and it seems other's) experience is that PB does NOT work "straight out of the box". I'd guess that the PB devs, etc installed this or that .so or package three years ago and have forgotten it, but it's "chaining up to dead-ends" when the system tries to initialize.
It seems to me that the problem here is probably a lack of of testing and documentation - Should PB be running from a folder on the desktop? Should it be in /usr/share or maybe /bin/ ? Should I sudo it to ensure the compiler loads? There seems to be no clarification other than "Just unpack it and it
should run from...."
And
"should" it just not good enough.
What we need is clarification and while I realise Linux is a pain (
because it's so configurable, customizable and powerful) PB (IMHO) is beginning to fall into the M$DN trap where the "documentation" says little more than:
"Function: Find(var_Find1, var_Find2_, [Bool_ChristAloneKnows])"
Finds ..um... stuff in... other er... stuff.
Was this article helpful?
[] Yes
[] No
[] Thank god for Google
[] The barrel is already in my mouth
Should've ducked faster.