bug-global
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Global 4.8.2 + external Berkeley DB


From: Luke Bakken
Subject: Global 4.8.2 + external Berkeley DB
Date: Fri, 31 Dec 2004 10:38:45 -0800

I've attached the version of global that I use in my work environment
(minus the parser I wrote for our proprietary programming language). I
have updated it to detect and use an external Berkeley DB installation
with the --with-berkeley-db configure option. I am going to do some
speed tests to see if using a new berkeley db version is faster than
the included one with global.

I have also made the following changes:

1. It is compatible with MinGW on Windows. In fact, I have done all of
my development (autoconf, automake) on Windows + MinGW. The 'w32'
directory is back. db.m4 is from the Apache project and detects which
Berkeley DB version is available. I have not yet compiled older
versions to ensure that they are compatible with Global, but I plan to
do so.

Bugs:
1.1 reconf.sh gives this warning. I don't think it's harmful but I
haven't figured out how to get rid of it yet:
configure.ac:46: warning: file `db.m4' included several times

2. The 'global.cgi' program now runs on Windows and UNIX. Windows
versions of perl do not support the 'open ... exec' syntax to avoid
shell processing. I also updated global.cgi to 'use strict'. There is
no reason to not use perl 5 syntax in this file since the 'open ...
exec' statement requires recent versions of perl anyway.

Bugs:
2.1 When the @PERL@ statement is turned into the perl path in MinGW,
/bin/perl is used. Most perl installations on Windows are in
c:/perl/bin/. The share/gtags/global.cgi.tmpl file will have to be
manually fixed by the user on a Windows system for now. The user may
also have to modify $ENV{PATH} in this file to include the global bin
directory. I plan on adding this to htags for when it creates the
global.cgi program.

One thing I have noticed is that the new C version of htags runs in 21
minutes on one of my source trees. The modified perl version that I
submitted several months ago (and am currently using) ran in 24
minutes. I expected a better improvement! How can we speed up htags
further do you think?

Thanks for a great product - I couldn't be as productive without it.
Luke

Attachment: global-4.8.2.zip
Description: Zip compressed data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]