Not really a compiling problem

Trying to build your own version of Vega Strike and having problems? Unix users, paste your config.log here (stderr output alone is not helpful).
Post Reply
rigelan
Confed Special Operative
Confed Special Operative
Posts: 291
Joined: Sat Jan 28, 2006 2:58 am
Location: Des Moines, Iowa

Not really a compiling problem

Post by rigelan »

It isn't really a compiling problem, per se. But I've tried to use the old vegastrike (4.3) binary with the new (svn current) data4.x folder information. When the binary exits, it gives a crash of

File "../data4.x/modules/universe.py", line 130, in significantUnits iter.advanceNSignificant(0)

AttributeError: advanceNSignificant

I was wondering if there was a quick hack to get this going. (I have somewhat suspended my trial of trying to compile the newest vegastrike binary for linux. Had some alut problems.) Is it possible to get the new data going with the old binary?
dandandaman
Artisan
Artisan
Posts: 1270
Joined: Fri Jan 03, 2003 3:27 am
Location: Perth, Western Australia
Contact:

Post by dandandaman »

Not with the new python stuff, no. However, one of the newer privateer binaries should work okay...

Dan
"Computers are useless. They can only give you answers."
-- Pablo Picasso
Post Reply