cscope-devel

Re: [Cscope-devel] Source Freeze now: Tagged 15.0bl1

[Joshua U. <uz...@li...>]

* Petr Sorfa <pe...@us...> [000426 13:21]:
> No changes to the source tree till I give the all clear.
> I've tagged the current source state as v15_0_bl1.
> As of now we can consider the source to be version 15.0 bl2

Cool... so are we going to be putting 15.0bl1 tarballs/rpms
available for download?

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

* Mike Hopkirk(hops) <ho...@sc...> [000426 13:21]:
> I downloaded the tarball a coupla hours ago and have been run 
> testing it on OSr5. 
> Good job it works pretty well. - No problems with building using lex
> 
> with flex however....
> 
> On our systems flex gets installed under /usr/local. 
> The configure run doesn't setup to search there so the yywrap test fails 
> and -lfl doesn't get added to the build line.
> 
> I hand coded round that wiring -L/usr/local/lib for the probe compile
> but then the build fails cos even tho its been told to use sysvcurses 
> it picks up the ncurses library (as curses) from /usr/local/lib (:-(

Hrmm... any you tried doing a "make distclean" and/or killing the
config.cache?  The flex/lex detector is standard with automake,
the curses detection is something I swiped from elsewhere (that was
also swiped from elsewhere).  Actually, on second thought, yes... I'll
look at ways of doing that...

> What I suggest is this:
> 
> Can we modify the configure to probe for the existance of the library and 
> if its not in /lib or /usr/lib add a -L/usr/local/lib to the macro 
> containing 'fl'
> (or alternatively add a -L/usr/local/lib regardless on the assumption
>     that if its not there it'll be found in the course of the normal
> system places search  .. ?? )

Sure... I'll see if that's possible...

> In addition change the assembly of the link line so that 
> LEXLIB is after CURSES_LIBS ( i.e last)
> 
> i.e Makefile.{am,in}
> cscope_LDADD = @LEXLIB@ @CURSES_LIBS@ 
> becomes 
> cscope_LDADD = @CURSES_LIBS@ @LEXLIB@

No problem.

> Is it possible to get a configure switch specifying which of 
> flex or lex to use ( for where flex is installed but want to build with lex)
> (I guess ditto for bison/lex)
 
Not sure... you could just "setenv LEX lex" or "setenv YACC yacc"
to override it... but a --with-lex= would take some work... maybe
for the future... I don't know how to do it off-hand.

> Whats with the SCO_FLAVOR settings in config.h and -D_SVID3 on build line ?
> Nothing in the sources uses them.

Those are as a result of the curses stuff I've put in... they're
there just in case we can use them to our benefit.

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] autoconf setup

[Petr S. <pe...@sc...>]

Hi Mike,

Job well done Joshua!

Just a couple of problems that Mike is experiencing as well.

On UnixWare 7, same flex problem as Mike reports for OSR5. Also I don't
have ncurses and for some reason libcurses does not get picked up.

Johsua want to look into these problems? Is there some kind of way of
debugging configure functions?

Petr

> On Tue Apr 25,2000 (10:08:27PM -0700), uz...@li...(Joshua Uziel) wrote:
> > * Petr Sorfa <pe...@sc...> [000424 21:16]:
> > > If anyboy wants to do the autoconf, go ahead and let me know. I'll
> > > freeze the code till autoconf is ready to go in. I'll freeze it only
> > > when Joshua's changes go in. I'm rather busy and will really only have
> > > time to look at the code on wednesday.
> >
> > Ok, I'm mostly ready to go on this... there's quite a bit to change,
> > though... so it might be better if I give you a tar ball and let you
> > merge it in.  I've kept the tree here up to date with the CVS tree
> > and the changes happening there.
> >
> > Mike - any results over there?  No matter, I have a new tarball
> > for you to try anyways...
> 
> I downloaded the tarball a coupla hours ago and have been run
> testing it on OSr5.
> Good job it works pretty well. - No problems with building using lex
> 
> with flex however....
> 
> On our systems flex gets installed under /usr/local.
> The configure run doesn't setup to search there so the yywrap test fails
> and -lfl doesn't get added to the build line.
> 
> I hand coded round that wiring -L/usr/local/lib for the probe compile
> but then the build fails cos even tho its been told to use sysvcurses
> it picks up the ncurses library (as curses) from /usr/local/lib (:-(
> 
> What I suggest is this:
> 
> Can we modify the configure to probe for the existance of the library and
> if its not in /lib or /usr/lib add a -L/usr/local/lib to the macro
> containing 'fl'
> (or alternatively add a -L/usr/local/lib regardless on the assumption
>     that if its not there it'll be found in the course of the normal
> system places search  .. ?? )
> 
> In addition change the assembly of the link line so that
> LEXLIB is after CURSES_LIBS ( i.e last)
> 
> i.e Makefile.{am,in}
> cscope_LDADD = @LEXLIB@ @CURSES_LIBS@
> becomes
> cscope_LDADD = @CURSES_LIBS@ @LEXLIB@
> 
> Is it possible to get a configure switch specifying which of
> flex or lex to use ( for where flex is installed but want to build with lex)
> (I guess ditto for bison/lex)
> 
> Whats with the SCO_FLAVOR settings in config.h and -D_SVID3 on build line ?
> Nothing in the sources uses them.
> 
> --
> - hops
> 
> Everything disclaimed (including disclaimer)
> ------<ho...@sc...>--------------------------------------
> Mike Hopkirk (hops)  |       Whenever possible steal code.
> SCO Inc              |          Tom Duff. (ex) Bell Labs
> 
> _______________________________________________
> Cscope-devel mailing list
> Csc...@li...
> http://lists.sourceforge.net/mailman/listinfo/cscope-devel

-- 
--------------------------------------------------------
Petr Sorfa                  Software Engineer
Santa Cruz Operation (SCO)  
430 Mountain Ave.           http://www.sco.com
Murray Hill 07974
NJ, USA
--------------------------------------------------------
Disclaimer: All my comments are my own and nobody else's
----------------------------------------------------------

Re: [Cscope-devel] autoconf setup

[Mike Hopkirk(hops) <ho...@sc...>]

On Tue Apr 25,2000 (10:08:27PM -0700), uz...@li...(Joshua Uziel) wrote:
> * Petr Sorfa <pe...@sc...> [000424 21:16]:
> > If anyboy wants to do the autoconf, go ahead and let me know. I'll
> > freeze the code till autoconf is ready to go in. I'll freeze it only
> > when Joshua's changes go in. I'm rather busy and will really only have
> > time to look at the code on wednesday.
> 
> Ok, I'm mostly ready to go on this... there's quite a bit to change,
> though... so it might be better if I give you a tar ball and let you
> merge it in.  I've kept the tree here up to date with the CVS tree
> and the changes happening there.
> 
> Mike - any results over there?  No matter, I have a new tarball
> for you to try anyways...


I downloaded the tarball a coupla hours ago and have been run 
testing it on OSr5. 
Good job it works pretty well. - No problems with building using lex

with flex however....

On our systems flex gets installed under /usr/local. 
The configure run doesn't setup to search there so the yywrap test fails 
and -lfl doesn't get added to the build line.

I hand coded round that wiring -L/usr/local/lib for the probe compile
but then the build fails cos even tho its been told to use sysvcurses 
it picks up the ncurses library (as curses) from /usr/local/lib (:-(

What I suggest is this:

Can we modify the configure to probe for the existance of the library and 
if its not in /lib or /usr/lib add a -L/usr/local/lib to the macro 
containing 'fl'
(or alternatively add a -L/usr/local/lib regardless on the assumption
    that if its not there it'll be found in the course of the normal
system places search  .. ?? )

In addition change the assembly of the link line so that 
LEXLIB is after CURSES_LIBS ( i.e last)

i.e Makefile.{am,in}
cscope_LDADD = @LEXLIB@ @CURSES_LIBS@ 
becomes 
cscope_LDADD = @CURSES_LIBS@ @LEXLIB@

Is it possible to get a configure switch specifying which of 
flex or lex to use ( for where flex is installed but want to build with lex)
(I guess ditto for bison/lex)


Whats with the SCO_FLAVOR settings in config.h and -D_SVID3 on build line ?
Nothing in the sources uses them.



-- 
- hops

Everything disclaimed (including disclaimer)
------<ho...@sc...>--------------------------------------
Mike Hopkirk (hops)  |       Whenever possible steal code.
SCO Inc              |          Tom Duff. (ex) Bell Labs

[Cscope-devel] Source Freeze now: Tagged 15.0bl1

[Petr S. <pe...@us...>]

Hi All,

No changes to the source tree till I give the all clear.

I've tagged the current source state as v15_0_bl1.

As of now we can consider the source to be version 15.0 bl2

Petr

Re: [Cscope-devel] Minor fixes and typo fix

[Joshua U. <uz...@li...>]

* Petr Sorfa <pe...@us...> [000426 11:50]:
> Added darrylo's patch to fix an unitialized variable and somebody pointed out
> that psuedo is spelt pseudo. All in.

Ok, and I just updated http://uzix.org/~uzi/cscope-ac.tar.gz
to reflect that.  The only difference in the "common"/"src"
diretory (besides the Makefile.ac and Makefile.in files) is
the "#include <config.h>" in both global.h and contants.h.

The big changes (that you should look at first) are in in
root of the tree (and there's a Makefile.{ac,in} in doc/).

Lemme know if/when you have questions...

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

[Cscope-devel] Minor fixes and typo fix

[Petr S. <pe...@us...>]

Hi,

Added darrylo's patch to fix an unitialized variable and somebody pointed out
that psuedo is spelt pseudo. All in.

Petr

Re: [Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

* Joshua Uziel <uz...@li...> [000426 01:45]:
> Petr - we should prod at my changes quite a bit and then
> merge this as the tree... I've make a *lot* of small changes
> to the source, all of which are needed for some reason or
> other...

Aww heck... I looked over the changes myself, and none of
then change really anything... just renamed some #defines
and variables (like one called "bool" to "boolarg" because
it was confusing some compilers).

I've committed those changes... so now the big stuff is
more the autoconf and automake stuff to look at... this
should make life easier on you now. :)

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

> I'll leave that up to you... the tree is in...
> 
> http://uzix.org/~uzi/cscope-ac.tar.gz

And hey, I've just now fixed a bunch more things... so if you've
grabbed it already, you're gonna want to grab it again.

So far, I know it works on Redhat, Debian, Solaris and OpenBSD.
A friend got it working on HPUX (but his system might be highly
modified), and NetBSD seems doable if someone with such a machine
wants to spend some time on it.  I've also heard that FreeBSD
works.

I guess the machines the hpux, osr5 and svr5 Makefiles were
meant for need to be tested as well...

Petr - we should prod at my changes quite a bit and then
merge this as the tree... I've make a *lot* of small changes
to the source, all of which are needed for some reason or
other...

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

* Petr Sorfa <pe...@sc...> [000424 21:16]:
> If anyboy wants to do the autoconf, go ahead and let me know. I'll
> freeze the code till autoconf is ready to go in. I'll freeze it only
> when Joshua's changes go in. I'm rather busy and will really only have
> time to look at the code on wednesday.

Ok, I'm mostly ready to go on this... there's quite a bit to change,
though... so it might be better if I give you a tar ball and let you
merge it in.  I've kept the tree here up to date with the CVS tree
and the changes happening there.

Mike - any results over there?  No matter, I have a new tarball
for you to try anyways...

> Joshua  I think you can go ahead and merge your changes with top of tree
> if you're comfortable, do a diff from your source to the tree before you
> do just in case you're working with missync'd code. More comments below:

I'll just give you the whole tree I have here and leave you to it.
This is a big enough change that I'll let you have a nice, long and
hard look at things before the commit.

> > * It'll default to "flex" and then go to "lex"... which flex seems
> >   to be required.  That, and I have it pass "-l" as an $LFLAG.
> Be careful not to let -l go to normal lex. Magic happens.

This is all fixed now... though a bit of it is a little hackish,
it works and should work right.

> Um, I had this dilema, and off hand I would say no as the scanner.c file
> relies on your proper setup of flex/lex anyway and the associated libl
> or libfl. Possibly with yacc file though.

And this was the biggest hack needed... but I got it working right
now so that neither generated file in distributed.  The nice thing
will be that when you want to put a new copy online for download,
you only need to do a "make dist" and it'll do everything for you.

> > * Setting the defines is not complete... "Linux" is there, but
> >   I'm not 100% sure about others like "BSD", etc...
> There is a BSD makefile, but I've not tested it.

The BSD makefile is _badly_ broken.  My friend with both an
OpenBSD and FreeBSD machine tried it and it didn't work.  My
autoconf stuff did work (after a few minor code changes) on
OpenBSD... and I haven't heard more about FreeBSD since...

> > * I have it -lcurses ... not -lncurses.  It's not problem on
> >   Linux, since they're one and the same.  I've noticed on Solaris
> >   (where this built fine) that it builds, and thinks it has
> >   ncurses, but then it can't find the shared library.  In the
> >   meantime, people can hand-modify it to use -lncurses after
> >   they do a ./configure.
> Look at the makefiles in the build directory for the differences.

Yep... worst case, we can hard-code things, but I don't think
there's an issue just using -lcurses.

> Sure drop in the INSTALL. Move the common directory to source as part of
> the autoconf setup.

I'll leave that up to you... the tree is in...

http://uzix.org/~uzi/cscope-ac.tar.gz

After this is tested to work, we should probably talk a bit more
before the merge, just in case... other that, I'm ready when you
are... and since I work from home mostly, my home/office phone
number is 510-794-2911... just in case you ever need/want it.

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] Fixed flex build break

[Mike Hopkirk(hops) <ho...@sc...>]

On Tue Apr 25,2000 (07:49:25AM -0700), pe...@us...(Petr Sorfa) wrote:
> Hi,
> 
> Whoops, my previous fix for non-flex lex broke the Linux build. Have fixed the problem.
> 
> We need to test this fix against non-flex lex on different operating systems.

Good stuff

Seems to work fine now using lex for building scanner on both osr5 and uw7.
think I'll revert the defaults for those Makefiles to lex rather than flex


-- 
- hops

Everything disclaimed (including disclaimer)
------<ho...@sc...>--------------------------------------
Mike Hopkirk (hops)  |       Whenever possible steal code.
SCO Inc              |          Tom Duff. (ex) Bell Labs

Re: [Cscope-devel] Added h to terse arg list for cscope

[Joshua U. <uz...@li...>]

* Petr Sorfa <pe...@us...> [000425 14:10]:
> Joshua omitted adding the h option to the terse arg list for cscope man page.

Ooops... and the -k option... added. :)

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

[Cscope-devel] Added h to terse arg list for cscope

[Petr S. <pe...@us...>]

Hi,

Joshua omitted adding the h option to the terse arg list for cscope man page.

Added.

Petr

[Cscope-devel] Fixed flex build break

[Petr S. <pe...@us...>]

Hi,

Whoops, my previous fix for non-flex lex broke the Linux build. Have fixed the problem.

We need to test this fix against non-flex lex on different operating systems.

Petr

[Cscope-devel] Updated scanner.l

[Petr S. <pe...@us...>]

Hi All,

Added a change to the scanner so that it supports the AT&T lex better.
Should not affect flex stuff at all.

Petr

Re: [Cscope-devel] -h option

[Joshua U. <uz...@li...>]

* Petr Sorfa <pe...@sc...> [000424 21:15]:
> > I've added a -h long usage help screen option.  Since --help
> > is on the TODO, I figured this was a first step at knocking
> > that off the list.
> Thanks, real nice. If you want you can try add the GNU standardish
> --help option or was that not that straight forward?

Well, just doing a '-h' was a slam dunk... I didn't look at the
"--help" variation too much.  Eh, we'll see... :)

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] autoconf setup

[Petr S. <pe...@sc...>]

Hi Joshua,

Sorry was out the whole day.

If anyboy wants to do the autoconf, go ahead and let me know. I'll
freeze the code till autoconf is ready to go in. I'll freeze it only
when Joshua's changes go in. I'm rather busy and will really only have
time to look at the code on wednesday.

Joshua  I think you can go ahead and merge your changes with top of tree
if you're comfortable, do a diff from your source to the tree before you
do just in case you're working with missync'd code. More comments below:

> * Mike Hopkirk(hops) <ho...@sc...> [000424 12:42]:
> > Let us know when you're happy with it and I'll test it on the systems
> > we've got here ( Osr5 and UW )
> 
> Yep, it's getting to a better state... the little messups are
> vanishing one-by-one... and it's starting to be portable.  A
> few thing to mention:
> 
> * It'll default on "bison -y", then go to "byacc" and then "yacc".
>   This doesn't seem to be a problem (though a little egrep.y
>   cleanup is needed to cut down on the warnings).
> 
> * It'll default to "flex" and then go to "lex"... which flex seems
>   to be required.  That, and I have it pass "-l" as an $LFLAG.
Be careful not to let -l go to normal lex. Magic happens.
> 
> * One thing is that both "egrep.c" and "scanner.c" are both being
>   included in the distribution when I do a "make dist" (very
>   handy if you've not used it before)... it can be averted if you
>   do a "make clean" ahead of time.  I don't know what your
>   preference is... my roommate (the GIMP maintainer) thinks it's
>   a good thing to include those files so as to cut down the need
>   for a lexer and a yacc (granted that they files still should be
>   included).  What do you guys think?
Um, I had this dilema, and off hand I would say no as the scanner.c file
relies on your proper setup of flex/lex anyway and the associated libl
or libfl. Possibly with yacc file though.

> * Setting the defines is not complete... "Linux" is there, but
>   I'm not 100% sure about others like "BSD", etc...
There is a BSD makefile, but I've not tested it.

> * I have it -lcurses ... not -lncurses.  It's not problem on
>   Linux, since they're one and the same.  I've noticed on Solaris
>   (where this built fine) that it builds, and thinks it has
>   ncurses, but then it can't find the shared library.  In the
>   meantime, people can hand-modify it to use -lncurses after
>   they do a ./configure.
Look at the makefiles in the build directory for the differences.

> 
> * Most things related to portability are probably either not
>   defined or not used.  But this will be a starting point...
>   and we can nail down issues of portability as we test building
>   on different OSes.
> 
> A bunch of new files will be introduced into the distribution.
> I also think it's a good idea to keep only the "doc", "contrib"
> and "common" directories... and to move "common" to "src".  Also,
> an "INSTALL" file is required... so one needs to be written (I've
> done the minimum).  I've also made some light source file
> modifications... but nothing major.
Sure drop in the INSTALL. Move the common directory to source as part of
the autoconf setup.
 
> Anyways... yeah... I've got it to a somewhat decent point... give
> this a whirl:  http://uzix.org/~uzi/cscope-ac.tgz
> 
> If you can get it working there, I'd say it's probably ready to
> go out the door, and portability fixes will occur when we get bug
> reports...
Ok sounds good,

Good work guys, lots of great progress.

Petr

> 
> --
> Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
> 415.354.4878 tel, 415.701.7457 fax
> uz...@li..., http://www.linuxcare.com/
> Linuxcare. Support for the revolution.
> 
> _______________________________________________
> Cscope-devel mailing list
> Csc...@li...
> http://lists.sourceforge.net/mailman/listinfo/cscope-devel

-- 
--------------------------------------------------------
Petr Sorfa                  Software Engineer
Santa Cruz Operation (SCO) 
430 Mountain Ave.           http://www.sco.com
Murray Hill 07974
NJ, USA
--------------------------------------------------------
Disclaimer: All my comments are my own and nobody else's
----------------------------------------------------------

Re: [Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

* Mike Hopkirk(hops) <ho...@sc...> [000424 12:42]:
> Let us know when you're happy with it and I'll test it on the systems 
> we've got here ( Osr5 and UW )

Yep, it's getting to a better state... the little messups are
vanishing one-by-one... and it's starting to be portable.  A
few thing to mention:

* It'll default on "bison -y", then go to "byacc" and then "yacc".
  This doesn't seem to be a problem (though a little egrep.y
  cleanup is needed to cut down on the warnings).

* It'll default to "flex" and then go to "lex"... which flex seems
  to be required.  That, and I have it pass "-l" as an $LFLAG.

* One thing is that both "egrep.c" and "scanner.c" are both being
  included in the distribution when I do a "make dist" (very
  handy if you've not used it before)... it can be averted if you
  do a "make clean" ahead of time.  I don't know what your
  preference is... my roommate (the GIMP maintainer) thinks it's
  a good thing to include those files so as to cut down the need
  for a lexer and a yacc (granted that they files still should be
  included).  What do you guys think?

* Setting the defines is not complete... "Linux" is there, but
  I'm not 100% sure about others like "BSD", etc...

* I have it -lcurses ... not -lncurses.  It's not problem on
  Linux, since they're one and the same.  I've noticed on Solaris
  (where this built fine) that it builds, and thinks it has
  ncurses, but then it can't find the shared library.  In the
  meantime, people can hand-modify it to use -lncurses after
  they do a ./configure.

* Most things related to portability are probably either not
  defined or not used.  But this will be a starting point...
  and we can nail down issues of portability as we test building
  on different OSes.

A bunch of new files will be introduced into the distribution.
I also think it's a good idea to keep only the "doc", "contrib"
and "common" directories... and to move "common" to "src".  Also,
an "INSTALL" file is required... so one needs to be written (I've
done the minimum).  I've also made some light source file
modifications... but nothing major.

Anyways... yeah... I've got it to a somewhat decent point... give
this a whirl:  http://uzix.org/~uzi/cscope-ac.tgz

If you can get it working there, I'd say it's probably ready to
go out the door, and portability fixes will occur when we get bug
reports...

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] -c and -k added to cscope.files

[Mike Hopkirk(hops) <ho...@sc...>]

On Mon Apr 24,2000 (12:49:36PM -0700), uz...@li...(Joshua Uziel) wrote:
> * Mike Hopkirk(hops) <ho...@sc...> [000424 12:42]:
> > cscope.dflt,  cscope.rc, .cscoperc.
> > 
> > Think its probably preferable to have this in a separate file 
> > (for base default values) looked for in home dir then cwd.
> > (traditional rc file handling)
> > 
> > Per project settings ( files and override switches) from cscope.files
> > in cwd.
> > 
> > The contents and parsing common to both.
> 
> Hrmm... the problem I have, is I think there should be something
> per-project that doesn't _require_ you to list files.  So if you
> have a cscope.files that just says "-c -k -q", and nothing else,
> it will build you a quick-indexed character cross-reference file
> without the /usr/include dir, and not further require you to list
> files you want to look at.  If you try that now, it'll say
> "cscope: no source files found" in a directory full of files.

Yah - should have an internal default glob pattern ( '*.[ch]' say)
that it uses if not overidden in rc file or on cmd line 

> > > I also noticed that there's an undocumented -o "OGS" option.
> > > What is this?
> > 
> > Looks like it was some handling for some sort of help system hook 
> > (dead ended fossil ??)
> 
> Yeah... that was my guess, too... waddaya think?  Strip it?

Yah probably ..

-- 
- hops

Everything disclaimed (including disclaimer)
------<ho...@sc...>--------------------------------------
Mike Hopkirk (hops)  |       Whenever possible steal code.
SCO Inc              |          Tom Duff. (ex) Bell Labs

Re: [Cscope-devel] -c and -k added to cscope.files

[Joshua U. <uz...@li...>]

* Mike Hopkirk(hops) <ho...@sc...> [000424 12:42]:
> cscope.dflt,  cscope.rc, .cscoperc.
> 
> Think its probably preferable to have this in a separate file 
> (for base default values) looked for in home dir then cwd.
> (traditional rc file handling)
> 
> Per project settings ( files and override switches) from cscope.files
> in cwd.
> 
> The contents and parsing common to both.

Hrmm... the problem I have, is I think there should be something
per-project that doesn't _require_ you to list files.  So if you
have a cscope.files that just says "-c -k -q", and nothing else,
it will build you a quick-indexed character cross-reference file
without the /usr/include dir, and not further require you to list
files you want to look at.  If you try that now, it'll say
"cscope: no source files found" in a directory full of files.
 
> > I also noticed that there's an undocumented -o "OGS" option.
> > What is this?
> 
> Looks like it was some handling for some sort of help system hook 
> (dead ended fossil ??)

Yeah... that was my guess, too... waddaya think?  Strip it?

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

Re: [Cscope-devel] -c and -k added to cscope.files

[Mike Hopkirk(hops) <ho...@sc...>]

On Sat Apr 22,2000 (03:46:54AM -0700), uz...@li...(Joshua Uziel) wrote:
> Since it causes no trouble and seemed approprate, I added the
> functionality of the cscope.files config file to handle both
> the -c and -k options.  It made sense, and I admit that for
> selfish reasons, it'll work well for a patch to the Linux
> Kernel's Makefile I want to submit after the next release
> of cscope (or maybe sooner, and I'll say it requires a version
> later than 13.0, so CVS for now).
> 
> Along with this is the thought... one of these two should
> happen:
> 
> a) cscope.files support be modified such that if no files are
>    listed, it treats the file as another means of supplying
>    options... and it goes and gets a default file list.
> b) another confile file (cscope.config?) is added to do the
>    functionality described in a).

cscope.dflt,  cscope.rc, .cscoperc.

Think its probably preferable to have this in a separate file 
(for base default values) looked for in home dir then cwd.
(traditional rc file handling)

Per project settings ( files and override switches) from cscope.files
in cwd.

The contents and parsing common to both.

 
> I think this becomes more important once you have a -R option
> instead of having to use cscope.files for large source trees.
> What do you guys think?
> 
> I also noticed that there's an undocumented -o "OGS" option.
> What is this?

Looks like it was some handling for some sort of help system hook 
(dead ended fossil ??)

-- 
- hops

Everything disclaimed (including disclaimer)
------<ho...@sc...>--------------------------------------
Mike Hopkirk (hops)  |       Whenever possible steal code.
SCO Inc              |          Tom Duff. (ex) Bell Labs

Re: [Cscope-devel] autoconf setup

[Mike Hopkirk(hops) <ho...@sc...>]

On Mon Apr 24,2000 (02:49:56AM -0700), uz...@li...(Joshua Uziel) wrote:
> So, what's going on with the autoconf setup?  

I'm not doing anything with that ... I think it was Petr's thing

> I ask, because as a learning exercise, I just got it kinda working over here. 

Cool.

As it
> is, one just needs to set $YACC to "yacc" and $LEX to "flex -l",
> and then it builds and works fine on Linux (haven't tried others
> yet).  Besides fixing that issue, there's a bit more meshing I
> need to do, cleanup and whatnot... but that should be doable and
> ready to go in the not-too-distant future...

Let us know when you're happy with it and I'll test it on the systems 
we've got here ( Osr5 and UW )


-- 
- hops

Everything disclaimed (including disclaimer)
------<ho...@sc...>--------------------------------------
Mike Hopkirk (hops)  |       Whenever possible steal code.
SCO Inc              |          Tom Duff. (ex) Bell Labs

[Cscope-devel] autoconf setup

[Joshua U. <uz...@li...>]

So, what's going on with the autoconf setup?  I ask, because as a
learning exercise, I just got it kinda working over here.  As it
is, one just needs to set $YACC to "yacc" and $LEX to "flex -l",
and then it builds and works fine on Linux (haven't tried others
yet).  Besides fixing that issue, there's a bit more meshing I
need to do, cleanup and whatnot... but that should be doable and
ready to go in the not-too-distant future...

(Partially because I live with the maintainer of the GIMP, so
this stuff is second nature to him... though I haven't pestered
him yet (and he's asleep right now)).

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

[Cscope-devel] -h option

[Joshua U. <uz...@li...>]

I've added a -h long usage help screen option.  Since --help
is on the TODO, I figured this was a first step at knocking
that off the list.

Files Modified: main.c cscope.1

Also, with my Delete key fix, I've found that it works fine
on Linux (x86 and SPARC) but not on Solaris (SPARC), so I guess
it may be a temporary fix... that or Solaris is being a PITA. :)

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.

[Cscope-devel] -c and -k added to cscope.files

[Joshua U. <uz...@li...>]

Since it causes no trouble and seemed approprate, I added the
functionality of the cscope.files config file to handle both
the -c and -k options.  It made sense, and I admit that for
selfish reasons, it'll work well for a patch to the Linux
Kernel's Makefile I want to submit after the next release
of cscope (or maybe sooner, and I'll say it requires a version
later than 13.0, so CVS for now).

Along with this is the thought... one of these two should
happen:

a) cscope.files support be modified such that if no files are
   listed, it treats the file as another means of supplying
   options... and it goes and gets a default file list.
b) another confile file (cscope.config?) is added to do the
   functionality described in a).

I think this becomes more important once you have a -R option
instead of having to use cscope.files for large source trees.
What do you guys think?

I also noticed that there's an undocumented -o "OGS" option.
What is this?

Files modified: dir.c global.h cscope.1

-- 
Joshua Uziel, Senior Linux Consultant, Linuxcare, Inc.
415.354.4878 tel, 415.701.7457 fax
uz...@li..., http://www.linuxcare.com/
Linuxcare. Support for the revolution.