This change is only helpful for you, but would break it for anyone getting the library/headers from somewhere else. A better way to do this would be to give configure the option for changing the headers path. Use CFLAGS and pass in the correct gcc option after it (-B is what it is methinks, but it has been awhile).Hai wrote:I got an error complaining the lzo1x.h could not be found during compilation with lzo2 enabled.
I edited crashlog.cpp and saveload/saveload.cpp and changed the include statement to
#include </opt/local/include/lzo/lzo1x.h>
from
#include <lzo/lzo1x.h>
to reflect the location of where macports installed lzo2 headers.
By the way, you can use LDFLAGS and the linker's -I option to add libraries to the search paths.
It seems like it would behoove you to read through some documentation on gcc so that you can solve the problems without making a mess of either your system or your code. All the symbolic linking and source code monkeying is unnecessary and permanently affects your system.
I hope this helps!
