[TRE-general] cygwin problem

skaller skaller at users.sourceforge.net
Wed May 10 18:36:00 EEST 2006


On Thu, 2006-05-11 at 00:38 +1000, skaller wrote:
> On Wed, 2006-05-10 at 13:34 +0300, Ville Laurikari wrote:
> > On Wed, May 10, 2006 at 07:00:16PM +1000, skaller wrote:
> > > Enable static? Hmmm. I need both static and dynamic libraries **
> > > I thought both were built (I have NO idea about what options
> > > the config script supports).
> > 
> > By default, TRE builds only a dynamic library.  You need to specify
> > --enable-static to get a static library too.
> 
> Actually, as you said this made the build go through. 
> {hmm .. didn't see the shared lib though .. but now
> I think of it I forget they go in 'bin' directory
> on cygwin/windws}

Sorry for multiple messages (dual booting Windows ..)

I just checked and --enable-static doesn't fix the real problem,
which is that shared libraries aren't being built at all.

Under current Cygwin, shared libraries work the same as on Linux
EXCEPT that they are named cygxxxx.dll. By convention,

	cygtre.dll

would be the name (cyg instead of lib, denoting dependence on 
cygwin1.dll). 

(The library has to go in bin directory I think, since Windows
searches for dlls on the PATH)

Note that there is no need with Cygwin to mess about with
any export/import libraries or other switches. It just works,
the same as for Linux (except for the library filename).
I.e. you do NOT need to make libtre.dll.a or whatever.
[This is fairly new, but it does work.. the whole of Felix
is linked with this magic :]

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net



More information about the TRE-general mailing list