Jump to content
The Dark Mod Forums

revelator

Development Role
  • Posts

    1174
  • Joined

  • Last visited

  • Days Won

    21

Everything posted by revelator

  1. well if your package manager does not have it then the only thing you can do is build it yourself though im wondering if it has a different name on your distro, which linux are you using ?.
  2. need to install the x86 version do sudo apt-get install libglew1.5-dev:i386 and you should hit jackpot
  3. since im running linux on a vm i cannot test the build so if anyone has a build done let me know if it works.
  4. stray leftover from removing GC, fixed on trunk now.
  5. Hehe i get very stubborn when something wont build Heres a test you can try http://sourceforge.net/projects/cbadvanced/files/gtkradiant/tdm_game02.pk4.tar.gz/download These are the compiled binaries from my kubuntu build.
  6. Full build done damn this was a bitch to get working, comitting final changes now.
  7. Annnd we have a winner took a few more fixes but it builds now.
  8. One error left im getting there undefined reference to glColorMask adding -lGL and -lGLU before linking with GLEW and hopefully we are done.
  9. Aye i just committed some new changes where im getting rid of the logging functions completely, it now runs to the end in scons but fails on linking to glew so i suspect the better way would be doing it the same way we do libjpeg and devil and simply compile in glew.c as part of the build. i noticed greebo made a lot of work in that department so if he could lend a hand i would be gratefull this is the only thing keeping it from building now.
  10. Got rid of the remaining qgl function pointers (seems i did not catch all of em the first round as there are also qgl pointers in the m4 files). Comitted to trunk feel free to test if it builds on linux now, still having problems with kubuntu :/
  11. Bit more than just the game code but thanks motorsep i will definatly look at it at some point.
  12. Also ok to discuss other stuff that might be of interrest lets just not derail it to much i think blender at one time supported md3 but yeah its not really something you should consider when doing a modern game. Also if the darkmod devs dont even use it i dont see much speaking for keeping it, IQM could be interresting to add but i might need a hand on that one if the devs want it in atleast. Atm ill focus on getting this building on linux/windows then we can allways go from there
  13. IQM is a skeletal model format if i remember correctly, and yeah md3 still has its uses . Ok got a bit further on the linux build but now it cannot find libpng (zlib problem again i suspect). no errors from m4 though and the generated files seem to be... well generated so my hopes up on that part.
  14. Not up to me but might be nice to have the support for some mod if you have a ton of md3 models laying around, best thing to do would be updating them to a newer format ofc.
  15. Gonna have a look at updating the devil sources to support the latest zlib, seems to be the only futureprof way.
  16. worked with idtech3 shaders and since the idtech4 shaders are an offshot of the former they should still work to some degree. I did i installed kubuntu unfortunatly the distro i selected used a version of zlib that devil is not happy with,and i cannot downgrade it it seems.
  17. i removed all those macros from m4 huh ?!?. Yep just checked those macros dont exist anywhere in the source, might be scons caching of things from old builds so it keeps picking them up, could you do a fresh checkout and build ? just in case.
  18. Not if using autotools they rely even more on m4 than scons, cmake maybe though i have to have a look at dhewm3 to see how that gets around it. I just installed kubuntu in wmware and tried a compile with my latest comitted changes and it builds but fails on devil because kubuntus zlib is to new, any hints on how to downgrade zlib ?.
  19. m4 is general purpose macro processor used in autotools normally and in doom3 for autogenerating headers and source files based on which opengl capabilities your linux distro has. It also requires knowledge im not sure posses when tinkering with it . Besides i have the grimm feeling that after the change to glew it cannot be fixed because some of the m4 chain also autogenerates some source files that we need so we cant simply remove it, even though most of that functionality is now provided by glew. Probably last try here, removed the defines for those function pointers from m4, if it does still not compile then we need someone with better understanding of the m4 macros to fix this im afraid. Changes have been committed. As for md3 support i wouldnt mind getting rid of it as its mostly a remnant of idtech3 code that seems to have been left in, its up to the modelers though if they want it removed ?.
  20. Heres something that might help on installing the official AMD drivers on ubuntu https://help.ubuntu.com/community/BinaryDriverHowto/AMD
  21. Do not give up to easily it took me quite a while to get to know linux when i first tried it many years back, todays distros have come a long way since then in terms of ease, back then the only way to install drivers was becomiing root and do it by shell commands (now thats nasty hehe). Not sure what distro you are using but the ubuntu line and offshots are probably the easiest to get around in, so might be a good idea to try one of those if you're not using it yet. It also has many ready made packages for pretty much anything you can think off. The gui is however not like most other distros that either use gnome or KDE, ubuntu uses there own gui system but its pretty easy to get around in so should not take long to understand where everything is. Could also try steamos though its still in beta you can get a premade iso from one of the guys on the sites forums that does not require UEFI and uses a visual installer instead of the shell scripts that are normally used for installing it. The repo is here http://repo.steampowered.com/download/ you can get the dvd iso from there. steamos uses debian which is also a good distro.
  22. True, also AMD drivers have a reputation of being rather unstable on linux :S i newer managed to get mine working correctly but i hope you have more luck.
  23. Ok removed that pointer and all vestiges of functions using it, crossing fingers. Edit comitted btw.
  24. Hmm seems the m4 defines are peppered with that damn pointer, guess ill have to kill off all of em, tbh i suspect i have to remove most of the m4 scripts since those functions are now handled by glew anyway and might collide with it.
×
×
  • Create New...