Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   Version of GCC to use?, posted by Steve Jones on Mon May 9 20:23:59 2005 
    icon2.gif   Re: Version of GCC to use?, posted by Stefan Ritt on Mon May 9 20:47:02 2005 
       icon2.gif   Re: Version of GCC to use?, posted by Steve Jones on Mon May 9 20:51:23 2005 
          icon2.gif   Re: Version of GCC to use?, posted by Stefan Ritt on Mon May 9 20:55:36 2005 
             icon14.gif   Re: Version of GCC to use?, posted by Steve Jones on Mon May 9 20:58:11 2005 
                icon14.gif   Re: Version of GCC to use?, posted by Steve Jones on Mon May 9 21:08:56 2005 
                   icon5.gif   Re: Version of GCC to use?, posted by Steve Jones on Mon May 9 21:14:53 2005 
                   icon14.gif   Re: Version of GCC to use?, posted by Stefan Ritt on Mon May 9 21:17:29 2005 
                      icon2.gif   Re: Version of GCC to use?, posted by Stefan Ritt on Mon May 9 21:22:46 2005 
                         icon14.gif   Re: Version of GCC to use?, posted by Steve Jones on Mon May 9 23:30:11 2005 
Message ID: 1144     Entry time: Mon May 9 21:17:29 2005     In reply to: 1142     Reply to this: 1145
Icon: Agree  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux | Other  ELOG Version: 2.5.9 
Subject: Re: Version of GCC to use? 
> Ok, now I see the issue - the tar extract created the mxml directory in the root (not
> under the created directory elog-2.5.9).  Is there a reason why these includes are not
> placed in the src dir like the regex.h/.c include?

Yes. I use these files in several other projects as well, and want to maintain only a
single copy. So I have

elogd-x.x.x/
elogd-x.x.x/src/
....
mxml/
mxml/strlcpy.h
mxml/strlcpy.c
mxml/mxml.c
mxml/mxml.c
...
other-project-x.x.x/
other-project-x.x.x/

So both elogd and "other-project" can use strlcpy.c and mxml.c. If I would copy it to
elogd-x.x.x/src and fix a bug there, "other-project" would use a separate copy and not
profit from the bug fix. So I would have to mainain verious copies of the same file, which
make things complicated. I compile everything also under windows, so I cannot use soft
links. If there is a better way of how to do it, please let me know.
ELOG V3.1.5-fe60aaf