development build installation

[feas]

So i used the optimistic installation script which seemed to go off without issue so that you for that work!

When I start ps from the development build installation (vice the regular client install) I get a few errors that point to crystal.  I don't know if they matter or not.

Here is a link to my  system info:

https://www.dropbox.com/s/hxlonfu409gwhqw/feas-system.txt?dl=0


The installation log:

https://www.dropbox.com/s/cfruv8zcr1d1g5m/ps-build-optimistic-install.txt?dl=0


The start up log:

https://www.dropbox.com/s/6emqvfh9m7adrkm/ps-build-start.txt?dl=0


I was hoping to install the developer build to see if I may be able to help with small stuff.

My system was updated prior to the install.

If I need to provide any additional info please let me know.

Thanks for looking

[redhound]

I suppose you trying to use scripts from my PlaneShift.BuildScripts project on GitHub... Well, it is not official project, you know. But I will look at the issue as soon as I'll have some free time to dig into it. Note that you could use project issue tracker to report bugs. Thanks for the feedback, anyway!

[feas]

Thank you. Not a rush as it does work with what I have done so far. It looks to me that alot of the errors stem from Crystal looking for a directory and files that do not exist for some reason.
It is from the jan 7 th post in these forums.

[redhound]

I have pretty same list of errors on builded client startup as you have. And only these lines are the extra ones comparing to the official client startup error list:
 

Code: [Select]

crystalspace.maploader:
  Could not find mesh factory ‘mesh_example’.
planeshift_effects:
  Couldn't find mesh factory mesh_example in effect mesh_example 
  Problem with an effect obj in: mesh/x_obj_mesh
crystalspace.maploader:
  Could not find mesh factory ‘mesh_example’.
planeshift_effects:
  Couldn't find mesh factory mesh_example in effect mesh_example2
  Problem with an effect obj in: mesh/x_obj_mesh

Don't know, does it affect something at run-time or not...

I've also noticed a configuration warning about missing 'libjpeg8-dev' in your logs. Debian 8 does not have this package, indeed. I've pushed update to 'ps-prereq-jessie.sh', replacing 'libjpeg8-dev' with 'libjpeg-dev'.