Re: [Somelib] _S_IFDIR is not defined

[Thomas M. <tma...@ze...>]

John Palmieri wrote:

> Thomas Matelich wrote:
>
> > OOPS!  Sorry about that, thought it would be faster.  _S_IFDIR *should* be
> > in <sys/stat.h>.  I figured since it is on Windows and HPUX that it would
> > be in Linux.  I don't think it would be a problem to change it back if you
> > want.
> >
>
> Well since they are platform specific we can just change them for linux or
> define _S_IFDIR under linux.
>

Apparently on linux, its called __S_IFDIR.  For convenience there is a macro
called S_IFDIR to call on the mode to check if it is a dir.


>
> >
> > On a related note, do we want to change Path so that it only searches for
> > dyn libs?  There could be problems (besides efficiency) if people have the
> > lib.1.1, lib.1, lib.so scheme I think.
> >
>
> Hmmm... Well I think that if a developer is using SOMELib they wouldn't load
> their whole /usr/lib directory.  The directory loading is for use when
> loading from say a plugin directory that only has lib.so.  Remeber that
> SOMELib takes care of versioning (Perhaps we should change versioning to
> three int's for comparison sake - ie major, minor and patch).  I plan to
> offer wildcard matching and text file loading (the textfile would specify
> what libs to load) in the future so that a developer could fine tune their
> lib loading.  Remember, C++ gives you the ability to format your HD, go into
> infinite loops, etc.  It doesn't meen a developer will use these "features".
> But they are there if a developer is crazy enough to want them.

If one is using kdevelop to create the shared libraries, it uses libtool which
automatically uses the versioning scheme I mentioned.  Therefore, I think it is
very important to only find the files with the correct extension.

--
Thomas O Matelich
Senior Software Designer
Zetec, Inc.
sos...@us...
tma...@ze...