a minimal www build for CVS import

I work for a small software company with a virtual organization.  The
people at my company work at home or at different office locales.

We do our development on multiple platforms (linux, Win32 and
Solaris).  Our source code is maintained in a central repository, and
we check it out using CVS over SSH.

To ease the maintenance of the different developers' development
environments, we've checked in the freely available tools we're using
(eg. libjpeg, zlib, libpng, pccts) into a 3rdparty directory.  

This is particularily important because we sometimes do testing with
different compilers on the same platform (eg. both gcc/egcs and SunPRO
C++ on Solaris).

I would like to put what I need to build libwww itself there, and
strip away all examples, documentation, and source code for a platform
I will never use (ie. vms), to minimize the network usage and disk
usage of a checked out workspace.  Say 3.3MB would be better than the
8.4MB of the entire checked out CVS tree.

But trying to strip down libwww raises some questions:
 1. does winConfigure.pl create platform specific header files?
    (ie. can I generate the .h files on linux, throw away the .html
    files they're generated from, and use the same .h files on Solaris 
    and Win32?)
 2. are any platform specific -D flags created by winConfigure.pl?  If
    so: which files do they come from and where do they go (which .h
    files)?
 3. Could/should I remove the ~500kB of prebuilt .dll and .lib files
    and build them myself?  (We already have a multiplatform makefile
    setup, using Troll Tech's tmake
        http://www.troll.no/announce/tmake-13.html
    )
 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? 

Those are the questions I can think of right now.  I'm sure there are
more...:-) 

I've been unable to find documentation that tells me what I need to
know, and haven't found anything useful when attempting to search the
mailing list archive.

Which means that I'm back to reading source code and experimenting.

This in turn means that any hints and tips will be *most* appreciated! :-)

Thanx!


- Steinar

Received on Thursday, 2 September 1999 10:18:40 UTC