Jump to content
The Dark Mod Forums

vlad

Member
  • Posts

    19
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. vlad@vladhome:~/aaa/gitrepos/dr-build> env LANG="C" make CDPATH="${ZSH_VERSION+.}:" && cd ./../darkradiant/darkradiant && /bin/sh /home/vlad/aaa/gitrepos/darkradiant/darkradiant/missing --run aclocal-1.11 -I m4 aclocal-1.11: couldn't open directory `m4': No such file or directory make: *** [../darkradiant/darkradiant/aclocal.m4] Error 1
  2. On my PC (OpenSUSE 11.2 x64) updater works well.
  3. I don't think so. I think that different versions of autotools aren't fully compatible with each other: they behave differently and make slightly different files. I'll post this error tonight.
  4. That's true, but I have to run autogen.sh before building DR. Otherwise, 'make' command doesn't work, it can't find some files. This script modifies all Makefile.in, configure and other generated files.
  5. As for me, there are some advantages: 1. It doesn't change the working copy; it doesn't generate files in working copy. 2. It compiles dm_editing plugin . Some months ago I tried to compile dm_editing, but there were some error messages. 3. Its syntax is simpler. That's good! I didn't try it before, because I supposed that DR needs its libs and files to be located in directories like /usr/local/share etc. Now I confirm that it works with custom prefix, but why it doesn't compile dm_editing?
  6. I've just written CMake scripts to build DR under Linux. I think CMake is more useful than Autotools. These scripts make a 'standalone' build of DR, you don't need to install DR, for example, in /usr/local. Here is the patch: http://depositfiles....files/xb0fde4ei Modified at 29 May 2010: Now you don't need to set LD_LIBRARY_PATH to run DR How to build: 1. Make an empty build directory and chdir to it: mkdir dr-build cd dr-build 2. Run cmake and set your installation prefix: cmake -DCMAKE_INSTALL_PREFIX=/home/vlad/dr_inst <darkradiant-source-root> 3. make install 4. enjoy;)
  7. Something is wrong with portal_sky and some other textures in Linux: these textures are black and transparent to entities.
  8. It seems that rev 5542 works good. There is one minor bug: http://img217.imageshack.us/img217/4271/screendro.jpg But it's rather old, can be spotted on Windows and can not prevent anyone from map editing.
  9. I've built the last revision. I can create brushes, but can't create entities or open maps -- DR crashes with segmentation fault. Some logs may be useful. crash at entity creation: crash at file opening:
  10. I'm at work too, and there is no doom3 and there are old boost libraries here. I can try to build it if I have free time, but probably I'll be able to build only at home.
  11. I've just finished bisecting The first bad revision is 5446 (Refactored entity KeyObservers into proper classes.)
  12. I've just started to search for the first bad revision. There is one small issue in the latest revision (5536): Makefile.in files are rather old, there aren't any references to radiant/log/GtkLogRedirector.cpp in radiant/Makefile.in. So build scripts should be regenerated with autoconf/automake, and only after that DR can be built. One more question: What's wrong with dm.editing plugin in Linux?
  13. It is the latest version that works on my PC, but I didn't try EVERY later revision. All later revisions that I built terminate with that boost exception. This exception appears before i18n branch. I can build some post-5437 trunk revisions and watch for exception if you want.
  14. There are problems in Linux with r5533. First of all, it doesn't build by default. Modules don't see GTK I18N headers and libs. I built DR only when I changed some Makefile.am files like that (here comes a patch): But this DR build doesn't work. When I try to open file or add some object, it crashes with a message: terminate called after throwing an instance of 'boost::exception_detail::clone_impl< boost::exception_detail::error_info_injector< boost::bad_weak_ptr> >' what(): tr1::bad_weak_ptr Now I use r5437; it works good.
×
×
  • Create New...