| Author |
Message
|
| hungerfish |
 Posted: Wed 30 Sep 2009 11:23 am Post subject: 1.32(svn 6043) |
 |
|
Joined: 02 Sep 2007
Posts: 70
|
I haven't the time to go digging at the moment, so I'll just ask:
What are the new/current dependencies to build edge (on linux) ?
| Quote: |
If you downloaded the EDGE source code from the SVN (Subversion)
repository, then you will need to add a copy of the GLBSP source
code, LUA 5.1 and possibly the other libraries which EDGE uses. |
Does the above still apply? What needs to be added?
This is my error:
| Code: |
| coal/c_memory.cc:157: error: 'memset' was not declared in this scope |
_________________
Call Apogee, Say "Aardwolf"!
Last edited by hungerfish on Wed 30 Sep 2009 3:59 pm; edited 1 time in total |
|
| Back to top |
|
 |
| andrewj |
| Posted: Wed 30 Sep 2009 12:13 pm Post subject: |
|
|
Joined: 05 May 2007
Posts: 599
Location: Tasmania
|
What you tried to compile is not 1.34 but "1.32SVN".
1.32SVN does not depend on glBSP or Lua.
The 1.34 code is in a separate folder trunk/n134 instead of trunk/edge
1.34 has the same dependencies as 1.31 including glBSP 2.24 and a c++ compiled Lua.
(See some recent posts in General Discussions for more information about the two codebases).
As for your specific problem, c_memory.cc was missing #include <string.h>, which I just added. |
|
| Back to top |
|
|
| hungerfish |
| Posted: Wed 30 Sep 2009 4:29 pm Post subject: |
|
|
Joined: 02 Sep 2007
Posts: 70
|
Ok, thanks! (I've changed this thread's title accordingly  )
I've been following the other threads, but I did indeed miss that there were now two actual code branches, instead of one.
Does 1.32(svn) actually build? Or is it 'supposed' to be build-able?
I did manage to get it built though, not without changing quite a few char * declarations to be const char *'s.
Also needed to add #include <algorithm> to src/tinybsp.cc
These were the errors:
| Code: |
ddf/image.cc:94: error: invalid conversion from 'const char*' to 'char*'
ddf/image.cc:222: error: invalid conversion from 'void (*)(char*, bool)' to 'void (*)(const char*, bool)'
ddf/states.cc:232: error: invalid conversion from 'const char*' to 'char*'
ddf/thing.cc:394: error: invalid conversion from 'const char*' to 'char*'
ddf/thing.cc:660: error: invalid conversion from 'const char*' to 'char*'
src/rad_pars.cc:324: error: invalid conversion from 'const char*' to 'char*'
src/rad_pars.cc:327: error: invalid conversion from 'const char*' to 'char*'
src/tinybsp.cc:769: error: 'sort' is not a member of 'std' |
I am running gcc4.4.1 
_________________
Call Apogee, Say "Aardwolf"! |
|
| Back to top |
|
|
| andrewj |
| Posted: Thu 01 Oct 2009 1:45 am Post subject: |
|
|
Joined: 05 May 2007
Posts: 599
Location: Tasmania
|
I checked out one of those errors, this line in ddf/states.cc:
| Code: |
| char *mid = strchr(info, '('); |
That code is VALID, as the manual page of strchr shows:
| Code: |
NAME
strchr, strrchr, strchrnul - locate character in string
SYNOPSIS
#include <string.h>
char *strchr(const char *s, int c);
char *strrchr(const char *s, int c);
#define _GNU_SOURCE
#include <string.h>
char *strchrnul(const char *s, int c);
|
So excuse me if I'm a bit pissed off at GCC (or whoever) changing the behavior of well established standards.
To say something more constructive: perhaps you can turn on C99 compability mode or something. |
|
| Back to top |
|
|
| andrewj |
| Posted: Sat 17 Oct 2009 1:24 am Post subject: |
|
|
Joined: 05 May 2007
Posts: 599
Location: Tasmania
|
Now that my nerd rage over GCC breaking things (yet again) has dissipated  , I have fixed those strchr() problems in the 1.34 codebase. |
|
| Back to top |
|
|
| hungerfish |
| Posted: Mon 19 Oct 2009 8:20 pm Post subject: |
|
|
Joined: 02 Sep 2007
Posts: 70
|
Good, good, keep that rage in check, it can become unhealthy at times
_________________
Call Apogee, Say "Aardwolf"! |
|
| Back to top |
|
|
|
|
