Great! That means that it will be a lot simpler to compile in Linux, whatever your setup. (Or in cygwin, BSD, ...)randy wrote:I'm working on making it use autoconf right now.
Linux progress
Moderator: GZDoom Developers
-
- Posts: 535
- Joined: Mon Aug 11, 2003 10:56 am
-
- Posts: 30
- Joined: Thu Dec 04, 2003 10:47 am
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Actually I find autoconf is a pain in the ass, I prefer some kind of a custom Makefile system myself.Jim wrote:Great! That means that it will be a lot simpler to compile in Linux, whatever your setup. (Or in cygwin, BSD, ...)randy wrote:I'm working on making it use autoconf right now.
For the end user, when the configure script breaks (which is very often on anything other than Linux), it is pure hell trying to clean things up to make things work.
EDIT: If randy wants to do this that is fine by me...
I just don't seen to see any advantages to using autoconf myself, other than to make things easier on the "./configure && make && make install" user but make things a pain in the ass when the script breaks, the user wants to change something, or isn't using Linux and/or a GNU userland.
-
- Posts: 31
- Joined: Mon Sep 01, 2003 2:02 pm
- Location: E2M2, among the many UAC boxes
That's cool, I can wait your next release.randy wrote:Would you like to see the source code before or after I autoconfiscate it? I'm working on making it use autoconf right now. But if you don't want to wait any longer, I still have the source with my custom Makefiles. (Although there is a crashing bug that kills it real quick which I introduced while trying to make it faster before starting the autoconf work.)
Actually, as long as ZDoom uses fmod for its sound routines, it kills pretty much any ports on other platforms (I guess fmod linux could run under FreeBSD, but I'm no expert on that).Jim wrote:Great! That means that it will be a lot simpler to compile in Linux, whatever your setup. (Or in cygwin, BSD, ...)
And of course, getting ZDoom to compile under cygwin is a pretty much a pointless effort.
Isn't it the actual idea behind autoconf/automake to have a portable build process? Yeah, I know it has its issues, but still... a well written autoconf script should only break on very badly designed systems, IMHO.akimmet wrote:Actually I find autoconf is a pain in the ass, I prefer some kind of a custom Makefile system myself.
For the end user, when the configure script breaks (which is very often on anything other than Linux), it is pure hell trying to clean things up to make things work.
EDIT: If randy wants to do this that is fine by me...
I just don't seen to see any advantages to using autoconf myself, other than to make things easier on the "./configure && make && make install" user but make things a pain in the ass when the script breaks, the user wants to change something, or isn't using Linux and/or a GNU userland.
-
- Posts: 535
- Joined: Mon Aug 11, 2003 10:56 am
Re: Linux progress
KDE 3.2.1, a maintenance release, has resolved many issues, including in KDevelop. I wonder if this recently fixed bug (http://bugs.kde.org/show_bug.cgi?id=71003) caused the problem you were refering to.randy wrote:I also miss having a decent integrated development environment under Linux like Visual Studio. KDevelop looked promising until I found out it can't handle projects with files in more than one directory.
-
-
- Posts: 10773
- Joined: Sun Jul 20, 2003 12:15 pm
-
- Posts: 1816
- Joined: Wed Jul 16, 2003 7:21 am
- Location: NJ, USA
-
- Posts: 2914
- Joined: Fri Dec 05, 2003 11:02 pm
-
- Posts: 10002
- Joined: Fri Jul 18, 2003 6:18 pm
- Location: Idaho Falls, ID
-
- Posts: 390
- Joined: Fri Aug 01, 2003 9:14 pm
-
- Posts: 5263
- Joined: Thu Jan 08, 2004 1:02 pm
- Location: N44°30' W073°05'
-
- Posts: 390
- Joined: Fri Aug 01, 2003 9:14 pm
-
- Posts: 390
- Joined: Fri Aug 01, 2003 9:14 pm