Well physfs is checked as availible but give an error as you say so i remove also this function and now i have next issue with OpenGL ...
Quote:
checking SDL_opengl.h usability... no checking SDL_opengl.h presence... no checking for SDL_opengl.h... no configure: error: SDL OpenGL header not found. Please install SDL with OpenGL support. /Work/SDK/Progetti/warzone2100-2.3.4>
checking for GL/glc.h... no configure: error: OpenGLC header not found. Please install QuesoGLC: http://quesoglc.sourceforge.net/
Also need this one. Not sure about this aswell.
Just for fun i removed the things that gave errors and ended up with this notice: configure: WARNING: Perl >= 5.10 isn't installed, autogeneration of some sources will not work.
Is it just failing a test in configure script? If so, it could be that just some dependency libs are missing. Please post the relevant part from config.log. It should say what went wrong with the test.
BTW have you set LDFLAGS=-use-dynld? If you don't then gcc will use static linking (.a) and not dynamic (.so).
Is it just failing a test in configure script? If so, it could be that just some dependency libs are missing. Please post the relevant part from config.log. It should say what went wrong with the test.
Yes it fails in configure
Here is what he say:
checking physfs.h usability... yes checking physfs.h presence... yes checking for physfs.h... yes checking for PHYSFS_init in -lphysfs... no configure: error: PhysicsFS not found.
This is the general command that I used for all my steps:
@samo79 I use libpsys for some ports and it works (so imho there some problems with patchs and so on, hope Salas00 can say how to fix it).
Quote:
Ok, where i need to add this specific command ? Into the main command and if so, when exactly ?
For now (imho) that is not problem about which you need to think. Its only about "how resulting binary will works", with sobjs (dinamic), or without (static). In general you not need to think about it at all for now (before we not have working makefile).
For now, you can also try to remove from configure script all about physfs at all (later you can add linking of library himself, that not so big problem). Those configure scripts are mess, and you can easiliy not remove something, or remove too much (be carefull here:) )
For now, you can also try to remove from configure script all about physfs at all (later you can add linking of library himself, that not so big problem). Those configure scripts are mess, and you can easiliy not remove something, or remove too much (be carefull here:)
Fine, so I will continue to test it removing that functions step by step
The rest isn't a big problem as in general I always mantain a proper backup of the entire source
Only things that isn't clear to me is how can this game will be compilable later if we remove its functions ...
You say, adding as link, but when, into the final makefile ?
Only things that isn't clear to me is how can this game will be compilable later if we remove its functions ...
There we remove not functions, but just that part of configure script, which can try to found where is liblibfs.a is placed (and by some reassons cant). But still, sources of game will have all that corrent includes, and everything will compiles fine to object files (which in end, on linking stage, will want that libpsys.a , which we will manually add to makefile if we will going to that final step).
Quote:
You say, adding as link, but when, into the final makefile ?
This configure script is infact one of the better i've seen. They have made comments when it starts on a new search. So removing checks is quite easy. So should be quite easy to get the makefiles made. And they are a few.
The only real and big problem about which i can think for now: its heavy dependences on X11 fucntions (maybe mos version was old one, while they not use X11, or maybe Fab (or who port it) just rewrite it a bit). Anyway, will see after saimo will have working makefile what errors he will have.
Ok, where i need to add this specific command ? Into the main command and if so, when exactly ?
Just add it to the end of the ./configure command line.
If this is not supported for some reason you can use setenv: setenv LDFLAGS -use-dynld
Or if you want to be certain that it's used: ./configure (...insert other options here...) "CC=gcc -mcrt=newlib -use-dynld" "CXX=g++ -mcrt=newlib -use-dynld"