Page 1 of 1

'yuni-config' not found

Posted: Thu Oct 14, 2010 11:55 am
by XChesser
I made a try to run new 2695 build but cmake fails:

Code: Select all

-- Looking for the Yuni Framework - failed ('yuni-config' not found)
CMake Error at CMakeLists.txt:66 (Message):
  The Yuni Framework could not be found.
Full output is attached.
Seems like I won't be able to play it in Sabayon :(

Re: 'yuni-config' not found

Posted: Sun Oct 17, 2010 12:12 pm
by zuzuf
ok, go to src/libs/yuni
and update your copy of Yuni to r1236:

Code: Select all

svn up -r 1236
This is not a definitive fix but it should let you built the game.

Re: 'yuni-config' not found

Posted: Sun Oct 17, 2010 12:33 pm
by milipili
There are a lot of code refactoring about the yuni-config / CMakeList in order to make the command 'make install' works and to provide a stable release. Sorry for inconvenience.

Re: 'yuni-config' not found

Posted: Sun Oct 17, 2010 12:54 pm
by zuzuf
Last revision should build normally :)

Re: 'yuni-config' not found

Posted: Mon Oct 18, 2010 1:45 pm
by XChesser
Thanks, now I can build the game. But it still crashes on units loading. Will wait for fixes :|

Re: 'yuni-config' not found

Posted: Mon Oct 18, 2010 3:46 pm
by zuzuf
Does it show up TA3D's crash report window ? If yes can you send the report please ?

Re: 'yuni-config' not found

Posted: Mon Oct 18, 2010 5:41 pm
by XChesser
No, not any window. I start skirmish, first loading goes well but on units loading stage it rapidly increases memory usage and crashes.
I've attached the log.

Re: 'yuni-config' not found

Posted: Mon Oct 18, 2010 8:16 pm
by zuzuf
I'll run a few tests on my netbook, it may be due to Intel chips sharing system memory.

Re: 'yuni-config' not found

Posted: Mon Oct 18, 2010 11:14 pm
by XChesser
I used to run ta3d about 2-3 years ago on this laptop. It was 0.5.x or 0.4.x version of ta3d. And I ran OpenSUSE 10.3 at that time.
So I think it is not hardware that causes this problem.

Re: 'yuni-config' not found

Posted: Tue Oct 19, 2010 3:41 pm
by zuzuf
The 0.6 branch is different from previous versions for many things because it uses SDL instead of Allegro/AllegroGL and all the low-level interfaces have been rewritten so it could be an hardware dependent bug.