This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
RE: attn cgf - single build integration
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Cygwin-Apps" <cygwin-apps at sources dot redhat dot com>
- Date: Sat, 27 Apr 2002 11:19:27 +1000
- Subject: RE: attn cgf - single build integration
> -----Original Message-----
> From: Robert Collins
> Sent: Saturday, April 20, 2002 9:50 AM
> To: Cygwin-Apps
> Subject: attn cgf - single build integration
>
>
> Chris,
> I'm approaching a point with libgetopt++ that I'll want
> to roll it into setup. This will (obviously) affect the
> single-build procress, so I'm hoping that you can confirm or
> suggest alterations to my plan:
>
> I think that as a general purpose library, it should sit at
> winsup/libgetopt++ or even a level above. However the binary
> linked into setup.exe needs to be built knowing about setup's
> String class (as opposed to the C++ standard basic_string).
>
> So here's my idea:
> we put the library at winsup/libgetopt++
> we make a symlink in the source tree at cinstall/libgetopt++
> to ../libgetopt++
>
> During configure time setup sub-configures libgetopt++ as a
> static only library in cinstall/libgetopt++
>
> In the future if any other programs want to start using it,
> we make winsup subconfigure winsup/libgetopt++.
>
> What do you think?
With setup moved, there is no current requirement to put libgetopt++ in
the winsup tree, so I won't be doing the above.
Of course, it's such a great library it should be there :}.
Rob