W3C home > Mailing lists > Public > www-lib@w3.org > July to September 1999

Re: a minimal www build for CVS import

From: Steinar Bang <sb@metis.no>
Date: 03 Sep 1999 12:54:30 +0200
To: www-lib@w3.org
Message-ID: <whlnao4655.fsf@viffer.oslo.metis.no>
>>>>> jose.kahan@w3.org:

> I made something similar for Amaya. I CVS tagged the parts of libwww
> that Amaya uses and removed the examples, doc, and other libwww
> applications.

This is the tag "Amaya"?  I found it when browsing through files in
        http://dev.w3.org/cgi-bin/cvsweb/libwww/Library/src/

Hm... this tag seems to follow the 5.2.8 release?  Or have you moved
it to get neccessary bugfixes?  Hm... for
        http://dev.w3.org/cgi-bin/cvsweb/libwww/Library/src/HTHost.c
the tag has been moved, so I guess the answer is "yes".

I did a 
   cvs -d :pserver:anonymous@dev.w3.org:/sources/public export -r Amaya libwww 

Is this the correct way to use the tag?  The results seem reasonable
at first look anyway.

Hm... expat wasn't there under modules, but I might as well get it
directly from James Clark.  Looks like the HTXML.c file was part of
the Amaya tag.

[snip!]
> No. You'll need to patch your Makefile though. There's a line there
> that checks if the .h files should be generated. It'll be better to
> remove it.

I'll go with my own tmake generated Makefile, I think.  So this will
probably not be a problem.

> No -D flags.

Good.  That would be more stuff to keep track of.  But there is a
Windows-specific config.h I need to include in
        libwww/Library/src

Is there a different config.h created by configure that I need to
include if I'm not on windows?  Hm... no... doesn't look like there is 
one in the complete checkout where I've configured and compiled libwww 
for Windows.  Where is the config.h file included from, I wonder...?

>> 4. Should I build the entire library as one .so (as tmake would
>> prefer for source in a single directory)?  Or should I try to use
>> some hack makefiles that would run the native libwww make setup?

> It all depends on your application. If you have many libwww
> applications, it makes sense to have DLLs rather than static
> libs.

I will make it into a DLL/.so but I will make it into a single .so
like you have done.  I will then strip down on the number of files
compiled when I know better exactly what I need (ie. I know already
that I won't need telnet og news functionality, but I won't strip them 
out until I know that things work with the full library).

[snip!]
> Hope this helps,

It sure does!  Thanx!


- Steinar
Received on Friday, 3 September 1999 06:54:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:15:17 UTC